From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6] socfpga: Adding Scan Manager driver
Date: Wed, 5 Mar 2014 17:13:44 +0100 [thread overview]
Message-ID: <20140305161344.GD20264@amd.pavel.ucw.cz> (raw)
In-Reply-To: <5315F57C.2010106@monstr.eu>
Hi!
> Also I expect that you can change all pins for uarts/ethernets/spi/i2c/etc
> that's why there is no golden configuration for socfpga that's why
> it is better to keep it empty just to compile it.
Well, there are some development boards around... and having u-boot
able to boot on the devel board by default would be very very useful.
> > At same time, these files are located inside board folders. If user have
> > different boards, they will have new set of folders here their own
> > handoff files. From there, there won't the need to regenerate everytime.
>
> Please explain me one thing how many users will use this configuration?
> Especially these ~600 lines?
Pretty much everyone when they test-boot their system...?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-03-05 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 16:03 [U-Boot] [PATCH v6] socfpga: Adding Scan Manager driver Chin Liang See
2014-02-28 10:17 ` Michal Simek
2014-03-04 15:01 ` Chin Liang See
2014-03-04 15:47 ` Michal Simek
2014-03-05 16:13 ` Pavel Machek [this message]
2014-03-05 18:47 ` Michal Simek
2014-03-05 19:00 ` Chin Liang See
2014-03-07 8:12 ` Michal Simek
2014-03-07 15:26 ` Chin Liang See
2014-03-03 20:41 ` Pavel Machek
2014-03-05 16:05 ` Chin Liang See
2014-03-05 16:15 ` Pavel Machek
2014-03-05 18:11 ` Chin Liang See
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=20140305161344.GD20264@amd.pavel.ucw.cz \
--to=pavel@denx.de \
--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