From: Krzysztof Halasa <khc@pm.waw.pl>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: Add support for IXP4xx CPU and for Goramo Multilink router platform.
Date: Sat, 08 Jan 2011 18:35:46 +0100 [thread overview]
Message-ID: <m3mxnbuwlp.fsf@intrepid.localdomain> (raw)
In-Reply-To: <20110108135522.GG12078@pengutronix.de> (Sascha Hauer's message of "Sat, 8 Jan 2011 14:55:22 +0100")
Sascha Hauer <s.hauer@pengutronix.de> writes:
>> This forces anyone to display with tabs=8 (vide the discussions on
>> lkml). Obviously one can decide to use tabs everywhere, I just want
>> to see such decision has been taken.
>
> Have there been discussions? Do you have a pointer?
It's been beaten to death, several times, along with the 80-column limit
(lifted some time ago). I think googling for "site:lkml.org tabs
alignment" should show relevant threads. My personal opinion is that
while we can easily use (and enforce) tabs for syntactic indentation,
other things should be left unruled.
IMHO the ideal situation is using spaces for anything other than
syntactic indentation, since it allows consistent viewing with any
tab length. Unfortunately, most of the editor programs are not there yet
(I'm told emacs can be told to do the "right thing" automatically).
> You could use a cramfs but it adds quite some binary size to the
> image. Is it even possible to share the firmware with Linux? I guess
> Linux does a request_firmware which either expects the firmware to be
> compiled in or under /lib/firmware.
Yes, the firmware must be in /lib/firmware/NPE-[ABC], but we could get
it, link etc. from cramfs. Even with a special tool reading cramfs and
writing files in /lib/firmware.
At present we simply have another copy of microcode in Linux image.
--
Krzysztof Halasa
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-01-08 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 14:48 New round of my IXP42x patches Krzysztof Halasa
2011-01-06 15:23 ` [PATCH 1/3] Fix error handling with malloc, memalign etc. Introduce xmemalign() Krzysztof Halasa
2011-01-06 15:25 ` [PATCH 2/3] ARM: support big/little endian switching in "bootX" Krzysztof Halasa
2011-01-06 15:26 ` [PATCH 3/3] ARM: Add support for IXP4xx CPU and for Goramo Multilink router platform Krzysztof Halasa
2011-01-06 23:36 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-08 12:16 ` Krzysztof Halasa
2011-01-08 13:55 ` Sascha Hauer
2011-01-08 17:35 ` Krzysztof Halasa [this message]
2011-01-08 18:10 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-09 12:03 ` Krzysztof Halasa
2011-01-08 13:33 ` Krzysztof Halasa
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=m3mxnbuwlp.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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