From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Enable writing to ATA devices, fix several bugs
Date: Sun, 20 Jul 2008 16:24:52 -0400 [thread overview]
Message-ID: <1216585492.14762.9.camel@dv> (raw)
In-Reply-To: <87iqv0idwz.fsf@xs4all.nl>
On Sun, 2008-07-20 at 20:55 +0200, Marco Gerards wrote:
> Pavel Roskin <proski@gnu.org> writes:
> > I know. That's why I'll write it from specifications or maybe I'll
> > take it from the GNU/Hurd code.
>
> Taking it from Specifications will be better.
>
> I think the ATA driver of GNU Mach comes from Linux 2.0 or so. So
> that won't change anything for us ;(.
I don't think choosing consistent names could be interpreted as a
copyright violation (except by companies like SCO, but then all bets are
off).
Anyway, if I ever have a chance to touch the GRUB ATA code again, I'll
use FreeBSD as a reference. Using specification is probably not the
best idea because we need GRUB to work on the real life hardware, and we
need to be prepared to handle known quirks in popular hardware.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-07-20 20:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 0:17 [PATCH] Enable writing to ATA devices, fix several bugs Pavel Roskin
2008-07-03 14:10 ` Robert Millan
2008-07-03 18:27 ` Marco Gerards
2008-07-03 20:50 ` Pavel Roskin
2008-07-04 11:50 ` Marco Gerards
2008-07-04 17:07 ` Pavel Roskin
2008-07-20 18:55 ` Marco Gerards
2008-07-20 20:24 ` Pavel Roskin [this message]
2008-07-21 12:49 ` Marco Gerards
2008-07-21 13:19 ` Javier Martín
2008-07-21 15:20 ` Marco Gerards
2008-07-21 15:33 ` Javier Martín
2008-07-21 15:56 ` Marco Gerards
2008-07-21 15:41 ` Pavel Roskin
2008-07-21 15:53 ` Marco Gerards
2008-07-21 16:00 ` Pavel Roskin
2008-07-21 16:10 ` Marco Gerards
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=1216585492.14762.9.camel@dv \
--to=proski@gnu.org \
--cc=grub-devel@gnu.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 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.