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 11:59:40 -0400 [thread overview]
Message-ID: <3D762DEC.C2517257@opersys.com> (raw)
In-Reply-To: 20020904145950.DRRI12451.rwcrmhc51.attbi.com@there
Mark,
Mark Meade wrote:
> I tested your Grub patch on a DoC Millennium, it works fine.
Great. I'm glad someone else can confirm that it works.
> I used the 0.92
> patch, but I had to reduce the length of some of the text messages to make
> everything fit. This may have been the gas 2.9.5 problem you described
> earlier.
True.
> This patch, while potentially useful during debugging, takes up precious
> space that may be needed later (to add support for new flash devices, etc).
> Also, once Grub is booting correctly from the DoC, I would think this feature
> would not be needed.
>
> For what it's worth, I'd recommend that this patch be made available in the
> patches directory of the CVS tree, rather than making it part of the official
> GRUB code.
This is one way of looking at it. However, it seems that this then enforces
a policy on the way developers use their hardware. Providing it as part of
the official GRUB and having it disabled by default would provide a capability
without enforcing a policy. A developer could then pass the
"--enable-doc-check-keybrd" option to "configure" in order to activate the
keyboard detection. This should be fairly easy to implement since all the
added code is enclosed in "#ifdef KEYBRD_READ" statements.
> I'm willing to revise my GRUB/DoC HOWTO to include instructions on the use of
> this patch, for those who are concerned about this issue.
A mention of any alternatives to the DOC hotplug would certainly be great.
Karim
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
next prev parent reply other threads:[~2002-09-04 15:55 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 [this message]
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
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=3D762DEC.C2517257@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.