From: Karim Yaghmour <karim@opersys.com>
To: Mark Meade <mark@lakeshoremicro.com>
Cc: linux-mtd@lists.infradead.org, Ilguiz Latypov <ilatypov@superbt.com>
Subject: Re: No more DoC hotplug on Grub fail [tested & working]
Date: Wed, 04 Sep 2002 14:33:11 -0400 [thread overview]
Message-ID: <3D7651E7.B3633688@opersys.com> (raw)
In-Reply-To: 20020904180749.DAXN1399.rwcrmhc51.attbi.com@there
Mark Meade wrote:
> Agreed.
Great, I'm glad there is a consensus on this.
> It's just a matter of making everything fit into a very limited
> space. As I mentioned earlier, maybe this feature is more valuable than the
> code that displays the manufacturer and chip ID codes. Another option would
> be to make the SHOW_INFO and KEYBRD_READ conditionals mutually exclusive.
Isn't there a way to get the manufacturer and chip ID codes display outside
the first 512 bytes? Couldn't the code for this go in stage2 instead? We
could then have the best of both worlds.
Karim
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
next prev parent reply other threads:[~2002-09-04 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 14:58 No more DoC hotplug on Grub fail [tested & working] Mark Meade
2002-09-04 15:27 ` Henrik Nordström
2002-09-04 15:59 ` Karim Yaghmour
2002-09-04 16:41 ` Henrik Nordstrom
2002-09-04 17:40 ` Mark Meade
2002-09-04 18:07 ` Mark Meade
2002-09-04 18:33 ` Karim Yaghmour [this message]
2002-09-04 19:15 ` Mark Meade
-- strict thread matches above, loose matches on Subject: below --
2002-08-11 8:00 Karim Yaghmour
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=3D7651E7.B3633688@opersys.com \
--to=karim@opersys.com \
--cc=ilatypov@superbt.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mark@lakeshoremicro.com \
/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