[meta-xilinx] what are the canonical xilinx mailing lists/repos these days?

[John Williams]

Hi Mike, Phil,

> -----Original Message-----
> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
> bounces at yoctoproject.org] On Behalf Of Mike Looijmans
> Sent: Wednesday, 7 August 2013 12:39 AM
> To: Philip Balister
> Cc: meta-xilinx at yoctoproject.org
> Subject: Re: [meta-xilinx] what are the canonical xilinx mailing lists/repos
> these days?
>
> On 08/06/2013 03:51 PM, Philip Balister wrote:
> > On 08/05/2013 01:53 AM, Mike Looijmans wrote:
> >> On 08/03/2013 09:24 PM, Michael Rissi wrote:
> >>> Dear all,
> >>> Just hooking up on the topic: For the zedboard, I tried out the
> >>> official meta-xilinx layer, as well as meta-zynq-milo.
> >>> Both worked great. meta-zynq-milo, however, has 2 main features I
> >>> liked a lot which are not in meta-xilinx:
> >>> - One can easily change the device where the root filesystem is
> >>> located by changing the file autorun.scr. This allows to easily
> >>> switch from rootfs over nfs  to e.g. the rootfs on the second
> >>> partition of the sd card.
> >>
> >> In fact you can do much more. For example, you can create an autorun
> >> SD card that automatically flashes a new image to the internal flash
> >> when you boot it. This is very convenient for low-volume production
> >> boards, which can then be programmed simply by inserting a card and
> >> switching it on.
> >>
> >> The change is only a small patch on u-boot, it mostly modifies the script.
> >>
> >> Also important is to note the change in load addresses. Loading the
> >> kernel directly into the correct memory location saves u-boot the
> >> trouble of memcpy-ing it there after unpacking.
> >>
> >> If you need any help, I'll be happy to provide it.
> >
> > The patch in question is:
> >
> > https://github.com/milosoftware/meta-zynq/blob/master/recipes-bsp/u-
> bo
> > ot/u-boot-zynq-git/0001-Use-bootscript-to-boot-use-fast-XIP-load-addre
> > ss-no-.patch
> >
> > It looks like this patch does several, unrelated, things. Spitting the
> > patch into independent chunks should make it easier to move into
> > u-boot and/or meta-xilinx.
>
> My initial setup had that, but there were too many changes going on in that
> same file, that it became too much of a burden to manage. And since I failed
> to raise any interest at Xilinx for these changes, I figured I might as well join
> them in a much easier to merge single patch.
>
> If anyone at xilinx is interested, I'll be happy to rebase and split this into
> useable chunks, and post the git patches wherever you want them.

Rather than managing patch fragments can you just work directly on the u-boot mailing list, cc:ing git at xilinx.com if necessary, and get it upstream?  Michal Simek is our u-boot maintainer, he's not on meta-xilinx at yocto list but you will certainly get his attention on the main u-boot list.

Regards,

John



This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.