[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] 1st SUZAKU patch for microblaze uClinux
At Tue, 17 Feb 2004 08:07:54 +1000,
John Williams wrote:
> Excellent, thanks for that. We'll get it into the CVS.
> > no contents has been changed.
> > regarding to the port, John, are you planing to create def-configs dir
> > in arch/microblaze like arm? if not, where should we keep default
> > configs?
> I modelled microblaze on the m68knommu way of doing this, which is to
> create a subdir for each platform in /vendors, containing the files
> config.linux-2.4.x, config.arch and config.uclibc, which are the default
> configs for the kernel, platform, and uClibc respectively.
> Is there something else about the arm def-config approach I should know
/vendor approach is fine if you got all uClinux-dist and do everything
in there. I usually keep dist and kernel in separate dir and use
only kernel dir to compile kernel.
to see the future, I believe (hope? ;) all uC port will be eventually
marged to linus' tree. at that point, we are separated from dist
package and need some way to keep default configuration for each board
in kernel tree.
# btw, is anyone working on 2.6 port?
> > other note, we, as in Atmark Techno, have been using Hermit as our
> > product's downloader/bootloader for a while. And I have a microblaze
> > port for that. It's still in alpha stage, but it's working for me on
> > my SUZAKU board.
> > If anyone is interested, it's here.
> Sounds great. The current bootloader is just a hangover from my early
> hacking, if we can get something a bit more robust with better features,
> I'm all for it.
I wish we could map flash at 0x0, so that we can boot from flash
directly. has anyone done that?
> > a sad thing is that EMC activates WE wrong number of times if we use
> > bus width matching. that force us to choose either '32bit fetch' or
> > 'ability to send command to flash'. we've chosen not to execute in
> > flash. :< that is, some program in bram need to copy hermit from flash
> > to dram.
> Did you notice that in EDK6.1, the EMC is distributed in EDK with full
> source (/edk/hw/XilinxProcessoIPLib/pcores/....)?
> So in principle you could change this behaviour to work as you need it.
> Also the license header in the sources asserts Xilinx copyright, but
> does not prohibit reproduction or modification.
> My personal interpretation is that you could modify this controller,
> note those changes in the header, and leave the Xilinx copyright notice,
> and not be breaking any rules.
hmm... It seems like you can't redistribute modification in source
form. did I miss interpret?
Maybe we are too much affected by free/open source world. ;P But, Our
intention is to keep original as much as we can, if we can't
redistribute our work.
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/