From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Some RFCs about U-Boot's the generic FPGA support
Date: Tue, 21 Aug 2007 10:30:19 +0200 [thread overview]
Message-ID: <200708211030.19721.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <OF569E3CF0.01976B6D-ON8825733D.00664661-8825733D.00671E4B@selinc.com>
Bruce,
On Monday 20 August 2007 20:46, Bruce_Leonard at selinc.com wrote:
> > 1) Make the 'size' parameter obsolete for the 'fpga loadb' command.
> > The actual bitstream size is taken from the bitstream.
>
> Agreed, plus you can remove the check against the size parameter passed in
> from the command line that doesn't make any sense.
Yes, I thought about that, too. But I wanted to take care about people using the
useless size parameter:-)
>
> >
> > 2) Do not bit-swap the bytes in the xilinx bitstream. When using the
> > slave serial code the bits may not be swapped. I can imagine that this
> > swapping requirement comes from a special board layout. So is should
> > be done in board specific code. When removing the swapping code, we
> > can get rid of the complete malloc/free stuff in fpga_loadbitstream().
>
> I would make this optional/configurable as I mentioned in my last post.
> Doing the bit swapping makes sense for a little endian processor but
> doesn't make sense for the big endian machines like the PPC.
Why? AFAIK, the _bit_order has nothing to do with die CPU endianess.
We are talking about mirrowing the 8 bits in a byte.
BTW, you can tell Xilinx promgen tool to use the other bitorder, so there is
no need to do correct it in U-Boot.
>
> >
> > 4) Make post() and pre() callback optional in relocation. So do
> > not relocate NULL-pointers. This has been discussed a short time ago
> > on the list.
>
> Agreed
>
> >
> > 6) Add some more devices.
> >
>
> More devices are always good. That way folks in the future have a
> starting place.
>
> >
> > BTW: Are there any boards that use the FPGA stuff and that are not
> > made public ?:-)
> >
>
> Our board is totally custom and will never be used by anyone but us, but
> as Wolfgang pointed out that's not the lists problem that's our problem.
> Folks using u-boot need to be aware that things change and they need to be
> careful when doing pulls from the repository.
Even totally custom boards should be in the U-Boot repository. Many boards
that are supported by U-Boot are custom boards. For examples esd
build more than 25 boards that are using U-Boot as bootloader. Less than 50%
of these boards are COTS product. The others are totally customized boards.
Matthias
next prev parent reply other threads:[~2007-08-21 8:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 13:13 [U-Boot-Users] Some RFCs about U-Boot's the generic FPGA support Matthias Fuchs
2007-08-20 13:47 ` Laurent Pinchart
2007-08-20 15:46 ` Matthias Fuchs
2007-08-21 8:59 ` Laurent Pinchart
2007-08-21 10:46 ` Matthias Fuchs
2007-08-21 11:33 ` Laurent Pinchart
2007-08-21 12:53 ` Matthias Fuchs
2007-08-21 20:09 ` Bruce_Leonard at selinc.com
2007-08-22 7:28 ` Laurent Pinchart
2007-08-22 7:59 ` Matthias Fuchs
2007-08-22 8:23 ` Laurent Pinchart
2007-08-22 17:12 ` Bruce_Leonard at selinc.com
2007-08-22 17:09 ` Bruce_Leonard at selinc.com
2007-08-22 17:33 ` Jerry Van Baren
2007-08-22 18:03 ` [U-Boot-Users] Loading vxWorks by u-boot Leonid
2007-08-22 19:40 ` Chris Fester
2007-08-22 20:12 ` Leonid
2007-08-22 20:42 ` Chris Fester
2007-08-22 21:18 ` Leonid
2007-08-22 20:12 ` Frank
2007-08-23 6:27 ` [U-Boot-Users] Antw: " Niklaus Giger
2007-10-09 20:04 ` [U-Boot-Users] Some RFCs about U-Boot's the generic FPGA support Bruce_Leonard at selinc.com
2007-08-23 7:41 ` Matthias Fuchs
2007-08-23 18:59 ` Bruce_Leonard at selinc.com
2007-08-20 13:52 ` Wolfgang Denk
2007-08-20 18:46 ` Bruce_Leonard at selinc.com
2007-08-21 8:30 ` Matthias Fuchs [this message]
2007-08-21 19:37 ` Bruce_Leonard at selinc.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200708211030.19721.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox