Re: [microblaze-uclinux] PetaLinux 0.20, including 2.6.20 kernel

[Peter Korsgaard <peter.korsgaard@xxxxxxxxx>]

>>>>> "L" == Leonid  <Leonid@xxxxxxxxx> writes:

Hi,

>> There's no future in kernel.org for the Xilinx drivers (_l, _g etc).
>> The only way drivers will make it to kernel.org is if they are
L> rewritten
>> in correct kernel style, as has happed for the uartlite and recently
>> system ace driver.

L> [Leonid] All Xilinx files must be rewritten or only such "external"
L> wrappers, containing the definitions in question?

Rewritten.

L> [Leonid] And how are you going to deal with same IP cores for different
L> architectures? Say, I have GPIO core and driver is the same no matter
L> where I use the core - in Spartan with Microblaze or in Virtex with
L> PPC405. Do you suggest to have independent copy (well, not exactly
L> "copy" - they will differ a little bit) of the same driver for each
L> architecture?

A single driver and setup code (struct platform_device) in each of the
platform files.

L> [Leonid] Building kernel is only part of creating working image, you
L> need root file system as well. You want have it in the form it can be
L> easily upgraded as new versions of particular packages are issued,
L> etc... This is sometimes tricky since not all packets are good for cross
L> compilation. In uClinux case you have everything in source; for other
L> architectures people use different approaches (like ad-hoc FS with
L> binaries and partially sources or set of RPMS, etc...). I just wanted to
L> learn your opinion regarding this problem.

Take a look at buildroot (http://buildroot.uclibc.org).

-- 
Bye, Peter Korsgaard
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/