Xilinx PowerPC
So when you have Xilinx under powerpc working, do we pull it from your git tree or the xilinx one ?
Will there be an announcement ?
How about a one paragraph getting started guide to moving a xilinx
ppc bsp to
xilinx powerpc.
Like ?
step 1).
Generate a dts - gen-mhs-devicetree ? And pass it to through your boot loader to Linux ?
Step 2).
the code in arch/powerpc/???? is the devicetree equvalent to arch/ppc/platforms/4xx/xilinx_ml410.c
Step 3).
device drivers need to change initialization/setup from ???? to ???
Just something to give those of us with no clue, a small one to start.
Thanks.
Quoted 4 lines
-----Original Message-----
From: [email protected]
[mailto:linuxppc-embedded-
Quoted 1 line
[email protected]] On Behalf Of David H.
Lynch Jr.
Quoted 6 lines
Sent: Wednesday, February 20, 2008 10:59 PM
To: Grant Likely; linuxppc-embedded
Subject: Xilinx PowerPC
=20
=20
So when you have Xilinx under powerpc working, do we pull it from
your
Quoted 5 lines
git tree or the xilinx one ?
=20
Will there be an announcement ?
=20
How about a one paragraph getting started guide to moving a xilinx
Quoted 8 lines
ppc bsp to
xilinx powerpc.
=20
Like ?
=20
step 1).
Generate a dts - gen-mhs-devicetree ? And pass it to through your boot loader to Linux ?
http://git.xilinx.com/gen-mhs-devtree.git contains two utilities for generating device trees from EDK projects. The older option is a python script, originally written by Grant. The newer (and probably more mature at this point) option is an EDK BSP generator for u-boot, originally written by Michal Simek. Preferably this gets passed from a uboot, although it's also possible to compile it into the kernel. Currently, the uboot option is somewhat annoying because there's not a good surefire way for getting uboot up and running on an EDK design. (Unfortunately, the EDK BSP generator is incomplete, and the uboot support for virtex needs some work to get it integrated as well).
Quoted 2 lines
Step 2).
the code inarch/powerpc/???? is the devicetree equvalent
to
Quoted 1 line
arch/ppc/platforms/4xx/xilinx_ml410.c
http://git.xilinx.com/linux-2.6-xlnx.git contains a preliminary stab at the bootcode for Virtex. I've been using this for a while with ARCH=3Dpowerpc. There isn't really much need for board specific = platform
code: This should (I think) be handled by the device tree. All of this is still pretty preliminary at the moment however. The big problem with the boot code in the Xilinx tree is that you need to be able to allocate memory in order to parse the device tree in order to figure out how much memory you have. I just haven't rewritten the code to use libfdt, which can query the device tree without memory allocation yet. Grant has a slightly different scheme in his tree, but it works as well. Generally I've been more focused on avoiding u-boot, whereas Grant has been using u-boot exclusively, I think.
Quoted 3 lines
Step 3).
device drivers need to change initialization/setup from
???? to ???All the xilinx drivers in mainline and most of the ones in the git.xilinx.com tree export both platform device and of_device interfaces. You should be able to look at any of them to figure out a good way of adding of_device support to a driver. the ll_temac is by far the most complex instance of this, which has to do some non-trivial traversal of the device tree to discover the information it needs about it's interface to memory.
So, the short answer is, you might be able to get it to work today, but the code isn't in shape for mainline yet.
Steve
Quoted 4 lines · Stephen Neuendorffer
Quoted 2 lines
Step 2).
the code inarch/powerpc/???? is the devicetree equvalentto
Quoted 1 line
arch/ppc/platforms/4xx/xilinx_ml410.c
Quoted 12 lines
http://git.xilinx.com/linux-2.6-xlnx.git contains a preliminary stab at the bootcode for Virtex. I've been using this for a while with ARCH=powerpc. There isn't really much need for board specific platform
code: This should (I think) be handled by the device tree. All of this is still pretty preliminary at the moment however. The big problem with the boot code in the Xilinx tree is that you need to be able to allocate memory in order to parse the device tree in order to figure out how much memory you have. I just haven't rewritten the code to use libfdt, which can query the device tree without memory allocation yet. Grant has a slightly different scheme in his tree, but it works as well. Generally I've been more focused on avoiding u-boot, whereas Grant has been using u-boot exclusively, I think.
Actually, I'm not using u-boot at all. I've reworked the 'raw' image target to use libfdt and properly initialize the cache and stuff. I'll be merging it in the .26 merge window.
Cheers,
g.
Signature · 2 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.
Quoted 10 lines
-- Original Message --
Date: Thu, 21 Feb 2008 12:02:21 -0700
From: "Grant Likely" <[email protected]>
To: "Stephen Neuendorffer" <[email protected]>
Subject: Re: Xilinx PowerPC
Cc: linuxppc-embedded <[email protected]>
Quoted 4 lines
Quoted 2 lines · Stephen Neuendorffer
Quoted 2 lines
Step 2).
the code inarch/powerpc/???? is the devicetree equval=
ent
Quoted 3 lines
Quoted 3 lines
to
Quoted 1 line
arch/ppc/platforms/4xx/xilinx_ml410.chttp://git.xilinx.com/linux-2.6-xlnx.git contains a preliminary stab
at
Quoted 2 lines
Quoted 2 lines
the bootcode for Virtex. I've been using this for a while with ARCH=3Dpowerpc. There isn't really much need for board specific plat=
form
Quoted 1 line
Quoted 1 line
code: This should (I think) be handled by the device tree. All of th=
is
Quoted 1 line
Quoted 1 line
is still pretty preliminary at the moment however. The big problem w=
ith
Quoted 1 line
Quoted 1 line
the boot code in the Xilinx tree is that you need to be able to alloc=
ate
Quoted 1 line
Quoted 1 line
memory in order to parse the device tree in order to figure out how m=
uch
Quoted 1 line
Quoted 1 line
memory you have. I just haven't rewritten the code to use libfdt, wh=
ich
Quoted 3 lines
Quoted 3 lines
can query the device tree without memory allocation yet. Grant has a=
slightly different scheme in his tree, but it works as well. General=
ly
Quoted 1 line
Quoted 1 line
I've been more focused on avoiding u-boot, whereas Grant has been usi=
ng
Quoted 6 lines
Quoted 1 line
u-boot exclusively, I think.
Actually, I'm not using u-boot at all. I've reworked the 'raw' image target to use libfdt and properly initialize the cache and stuff. I'll be merging it in the .26 merge window.
Hi,
Just wondering - is it possible to use U-Boot on the Xilinx XUPV2PRO board or any similar tools (such as libfdt?) to copy a Linux kernel and=
ramdisk filesystem from a SystemACE card to memory, uncompress them and=
boot the Linux kernel etc?? If so is there any notes/docs about how to
do
this or similar online anywhere?
Any info. appreciated,
Regards&Thanks,
Alan.
Quoted 5 lines
=20
Hi,
=20
Just wondering - is it possible to use U-Boot on the Xilinx XUPV2PRO board or any similar tools (such as libfdt?) to copy a Linux kernel
and
Quoted 2 lines
=20
ramdisk filesystem from a SystemACE card to memory, uncompress them
and
Quoted 2 lines
=20
boot the Linux kernel etc?? If so is there any notes/docs about how
to
Quoted 6 lines
do
this or similar online anywhere?
=20
Any info. appreciated,
Regards&Thanks,
Alan.
In theory, yes... All the infrastructure to do this exists, but I don't know of anyone who as actually tried it yet with ARCH=3Dpowerpc kernels. There=20
Steve
Quoted 30 lines
-- Original Message --
Subject: RE: Xilinx PowerPC
Date: Fri, 22 Feb 2008 10:11:19 -0800
From: "Stephen Neuendorffer" <[email protected]>
To: <[email protected]>,
"Grant Likely" <[email protected]>
Cc: linuxppc-embedded <[email protected]>Quoted 6 lines
Hi,
Just wondering - is it possible to use U-Boot on the Xilinx XUPV2PRO=
board or any similar tools (such as libfdt?) to copy a Linux kernel
and
Quoted 2 lines
ramdisk filesystem from a SystemACE card to memory, uncompress them
and
Quoted 2 lines
boot the Linux kernel etc?? If so is there any notes/docs about how
to
Quoted 6 lines
do
this or similar online anywhere?Any info. appreciated,
Regards&Thanks,
Alan.
Quoted 7 lines
In theory, yes... All the infrastructure to do this exists, but I don't=
know of anyone who as actually tried it yet with ARCH=3Dpowerpc kernels.=
There
Steve
So i can try the latest official U-Boot releases with the ML300 configur=
ation
or is there a port or similar of U-Boot for the Xilinx XUPV2PRO board??
Regards&Thanks,
Alan.
Quoted 23 lines
-----Original Message-----
From: Alan Casey [mailto:[email protected]]
Sent: Friday, February 22, 2008 10:58 AM
To: Stephen Neuendorffer; Grant Likely
Cc: linuxppc-embedded
Subject: RE: Xilinx PowerPC
=20
=20Quoted 13 lines
-- Original Message --
Subject: RE: Xilinx PowerPC
Date: Fri, 22 Feb 2008 10:11:19 -0800
From: "Stephen Neuendorffer" <[email protected]>
To: <[email protected]>,
"Grant Likely" <[email protected]>
Cc: linuxppc-embedded <[email protected]>Quoted 4 lines
Hi,
Just wondering - is it possible to use U-Boot on the Xilinx
XUPV2PRO
Quoted 1 line
Quoted 1 line
Quoted 1 line
board or any similar tools (such as libfdt?) to copy a Linux
kernel
Quoted 3 lines
Quoted 3 lines
and
Quoted 2 lines
ramdisk filesystem from a SystemACE card to memory, uncompress
them
Quoted 3 lines
Quoted 3 lines
and
Quoted 2 lines
boot the Linux kernel etc?? If so is there any notes/docs about
how
Quoted 9 lines
Quoted 9 lines
to
Quoted 6 lines
do
this or similar online anywhere?Any info. appreciated,
Regards&Thanks,
Alan.In theory, yes... All the infrastructure to do this exists, but I
don't
Quoted 1 line
Quoted 1 line
know of anyone who as actually tried it yet with ARCH=3Dpowerpc
kernels.
Quoted 5 lines
Quoted 3 lines
There
Steve
=20
So i can try the latest official U-Boot releases with the ML300
configuration
Quoted 1 line
or is there a port or similar of U-Boot for the Xilinx XUPV2PRO
board??
Quoted 5 lines
=20
Regards&Thanks,
Alan.
=20
=20
That's probably your best starting point.... There is a uboot application note on the Xilinx website (XAPP 542), but it's a little thin on porting information.
Steve
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 13 lines
-----Original Message-----
From: David H. Lynch Jr. [mailto:[email protected]]
Sent: Friday, February 22, 2008 1:51 PM
To: Stephen Neuendorffer
Cc: linuxppc-embedded
Subject: Re: Xilinx PowerPC
=20Quoted 3 lines · Stephen Neuendorffer
Quoted 3 lines
-----Original Message-----
From:
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
[mailto:linuxppc-embedded-
Quoted 1 line
[email protected]] On Behalf Of David =
H.
Quoted 9 lines
Quoted 9 lines
Quoted 1 line
Lynch Jr.
Quoted 6 lines
Sent: Wednesday, February 20, 2008 10:59 PM
To: Grant Likely; linuxppc-embedded
Subject: Xilinx PowerPCSo when you have Xilinx under powerpc working, do we pull it
from
Quoted 8 lines
Quoted 8 lines
Quoted 1 line
your
Quoted 5 lines
git tree or the xilinx one ?
Will there be an announcement ?
How about a one paragraph getting started guide to moving a
xilinx
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
ppc bsp to
xilinx powerpc.Like ?
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
step 1).
Generate a dts - gen-mhs-devicetree ? And pass it to through your boot loader to Linux ?http://git.xilinx.com/gen-mhs-devtree.git contains two utilities for generating device trees from EDK projects. The older option is a
python
Quoted 3 lines
Quoted 3 lines
script, originally written by Grant. The newer (and probably more mature at this point) option is an EDK BSP generator for u-boot, originally written by Michal Simek. Preferably this gets passed
from a
Quoted 2 lines
Quoted 2 lines
uboot, although it's also possible to compile it into the kernel. Currently, the uboot option is somewhat annoying because there's not
a
Quoted 7 lines
Quoted 4 lines
good surefire way for getting uboot up and running on an EDK design. (Unfortunately, the EDK BSP generator is incomplete, and the uboot support for virtex needs some work to get it integrated as well).
Thanks, I found the python script. Please do not fixate on u-boot.
it is not an option for us. We have our own bootloader.
it handles .elf files, fits in 16k or BRAM and just starts when
the
Quoted 6 lines
FPGA is loaded. We will have to added device tree support to it.
I had thought you were talking about appending the device tree to
the bitfile.
That sounds like a really good option for us.
=20
We also really don't have a great interest in the EDK BSP
generator.
Quoted 6 lines
We have our own BSP's for our cards for both GHS and Linux. Except the rare instances - like right now while we are
transitioning to the
newerLL_TEMAC, we use normal linux drivers, either from the
existing kernel
trees, or written inhouse.
The BSP generator is significantly different from the normal EDK Linux BSP. The key thing is that the device tree generated by the python script is necessarily incomplete, since it does not have information about default parameter values which appear in the core definitions. I would *highly recommend* using the uboot bsp to get a device tree. You can always ignore anything else that it does (or hack the code to your hearts content to do what you want, such as incorporating it into your own BSP).
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Step 2).
the code inarch/powerpc/???? is the devicetree
equvalent
Quoted 6 lines
Quoted 6 lines
Quoted 1 line
to
Quoted 2 lines
arch/ppc/platforms/4xx/xilinx_ml410.chttp://git.xilinx.com/linux-2.6-xlnx.git contains a preliminary stab
at
Quoted 2 lines
Quoted 2 lines
the bootcode for Virtex. I've been using this for a while with ARCH=3Dpowerpc. There isn't really much need for board specific
platform
Quoted 4 lines
Quoted 1 line
code: This should (I think) be handled by the device tree.
So I have a device tree for my card somehow. Presumably I need the
binary form.
My bootloader needs to pass a pointer to a copy in memory to
Linux.
Quoted 4 lines
=20
How do I config the linux from your git tree ?
Do I just config for a generic Xilinx card and the device tree
handles the rest ?
Essentially. There is a generic virtex configuration option.
Quoted 5 lines
Next we have a hosted pseudo serial port. Devict Trees could cope
with that.
But We also have early serial support for both it and Uartlite, Also our Linux BSP and UartLite drivers will work without a PIC. And would even do ethernet (badly) with the earlierLL_TEMAC
without
Quoted 2 lines
DMA and interrupts.
So do I modify the device tree to choose a different uartlite
driver ?
Quoted 1 line
I had to put a fair amount of patches in to support early serial
with
Quoted 1 line
non-8250 serial ports. Do I have to patch your generic xilinx BSP
to
Quoted 1 line
deal with that ?
Early serial on uartlite is works fine. You have to add an explicit reference to the uartlite to get it to work. Early serial on uart16550 doesn't work yet, because the device has an unusual spacing between the registers.
Quoted 1 line
Please do not develop a u-boot only solution.
I don't believe Linux will never *require* uboot.
Quoted 5 lines
Just to clarify, am I correct in presuming that say the uartlite
driver in the
xilinx git tree will handle either thearch/ppcstyle platform
device initialization
or thearch/powerpcdevicetree initialization ?
Yes. drivers are capable of probing both the platform bus and the of bus. It is expected that each device is advertised on only one. In general, ppc will advertise platform devices and powerpc will advertise of devices.
Quoted 3 lines
Is there some means of doing a phased transition ?
Can I lift the device tree BSP setup code into my own BSP, and then remove the platform device code peice by peice as things
work ?
probably, although changing the drivers is not challenging, as long as all the information you need is in the device tree.
Quoted 2 lines
Is there something magical about being physically located in
arch/ppcorarch/powerpc?
Well, ppc doesn't support of/device trees. All of the of bus stuff is #ifdef'd out of the drivers.
Steve
Hi All,
Quoted 10 lines
http://git.xilinx.com/gen-mhs-devtree.git contains two utilities for generating device trees from EDK projects. The older option is a python script, originally written by Grant. The newer (and probably more mature at this point) option is an EDK BSP generator for u-boot, originally written by Michal Simek. Preferably this gets passed from a uboot, although it's also possible to compile it into the kernel. Currently, the uboot option is somewhat annoying because there's not a good surefire way for getting uboot up and running on an EDK design. (Unfortunately, the EDK BSP generator is incomplete, and the uboot support for virtex needs some work to get it integrated as well).
U-BOOT part will be removed from EDK generator. The new name will be only fdt_v1.00.a. I have prepared separated version for FDT generation and for U-BOOT generation.
Steve: You can remove U-BOOT part from generator. This part is useful only for Microblaze cpu.
Regards,
Michal Simek
Michel,
I've had it on my todo list to get the u-boot stuff working for powerpc too... However, I remember a brief comment from John Williams that you'd separated the BSP generation process more. Details (or better yet, code and patches) would be appreciated, here, since I'm a bit swamped at the moment.
Steve
Quoted 11 lines
-----Original Message-----
From: Michal Simek [mailto:[email protected]]
Sent: Sunday, March 02, 2008 10:25 AM
To: Stephen Neuendorffer
Cc: David H. Lynch Jr.; Grant Likely; linuxppc-embedded
Subject: Re: Xilinx PowerPC
=20
Hi All,
=20Quoted 2 lines
http://git.xilinx.com/gen-mhs-devtree.git contains two utilities for generating device trees from EDK projects. The older option is a
python
Quoted 3 lines
Quoted 3 lines
script, originally written by Grant. The newer (and probably more mature at this point) option is an EDK BSP generator for u-boot, originally written by Michal Simek. Preferably this gets passed
from a
Quoted 2 lines
Quoted 2 lines
uboot, although it's also possible to compile it into the kernel. Currently, the uboot option is somewhat annoying because there's not
a
Quoted 5 lines
Quoted 3 lines
good surefire way for getting uboot up and running on an EDK design. (Unfortunately, the EDK BSP generator is incomplete, and the uboot support for virtex needs some work to get it integrated as well).
=20
U-BOOT part will be removed from EDK generator. The new name will be
only
Quoted 1 line
fdt_v1.00.a. I have prepared separated version for FDT generation and
for U-BOOT
Quoted 3 lines
generation.
=20
Steve: You can remove U-BOOT part from generator. This part is useful
only for
Quoted 4 lines
Microblaze cpu.
=20
Regards,
Michal Simek