From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PCI memory allocation bug with CONFIG_HIGHMEM
Date: 08 Jan 2004 12:34:48 -0700 [thread overview]
Message-ID: <m1smiqi693.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401070803320.12602@home.osdl.org>
Linus Torvalds <torvalds@osdl.org> writes:
> At some point, the _correct_ answer may be: don't do complex things, and
> write a bootable floppy (without any OS at all, or a really minimal one)
> to do BIOS rom updates.
ROM chips fall into the linux mtd layer quite cleanly, and they are
just quirky enough they need someplace where lots of eyes look at the
code, and lots of people use the code. And the linux mtd layer
appears to be that place.
I have had enough success in actually using the linux kernel, for
flashing ROMS, it is becoming worth while to actually fix up the
last couple of annoying cases.
Plus I'm close to the point of finding some value in jffs2 and the
other flash filesystems, at which point I will need to use the mtd
layer anyway.
Eric
next prev parent reply other threads:[~2004-01-08 19:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1aJdi-7TH-25@gated-at.bofh.it>
2004-01-06 3:32 ` Andi Kleen
2004-01-06 3:40 ` Linus Torvalds
2004-01-06 4:05 ` Andi Kleen
2004-01-06 5:04 ` Linus Torvalds
2004-01-06 8:12 ` Andi Kleen
2004-01-06 9:11 ` Mika Penttilä
2004-01-06 9:44 ` Andi Kleen
2004-01-06 10:16 ` Mika Penttilä
2004-01-06 10:49 ` Andi Kleen
2004-01-06 15:27 ` Linus Torvalds
2004-01-06 15:37 ` Andi Kleen
2004-01-06 15:48 ` Linus Torvalds
2004-01-06 22:29 ` Adam Belay
2004-01-07 4:06 ` Linus Torvalds
2004-01-07 5:02 ` Andi Kleen
2004-01-07 5:55 ` Dave Jones
2004-01-07 6:06 ` Linus Torvalds
2004-01-07 6:08 ` Dave Jones
2004-01-07 6:45 ` Linus Torvalds
2004-01-07 6:51 ` Andi Kleen
2004-01-07 2:43 ` Adam Belay
2004-01-07 8:32 ` Helge Hafting
2004-01-06 22:45 ` Eric W. Biederman
2004-01-07 0:06 ` Linus Torvalds
2004-01-07 4:58 ` Eric W. Biederman
2004-01-07 5:32 ` Linus Torvalds
2004-01-07 15:53 ` Eric W. Biederman
2004-01-07 16:32 ` Linus Torvalds
2004-01-07 17:32 ` Eric W. Biederman
2004-01-08 19:34 ` Eric W. Biederman [this message]
2004-01-07 9:31 ` Russell King
2004-01-07 15:06 ` Eric W. Biederman
2004-01-07 20:29 ` Russell King
2004-01-06 22:56 ` Eric W. Biederman
2004-01-05 20:07 David Hinds
2004-01-05 23:00 ` Russell King
2004-01-05 23:45 ` David Hinds
2004-01-06 0:36 ` Linus Torvalds
2004-01-06 0:44 ` David Hinds
2004-01-06 1:11 ` Linus Torvalds
2004-01-06 1:41 ` Linus Torvalds
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=m1smiqi693.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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
all inboxes | Powered by JetHome®