All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH]: Fix CDROM skipping in ieee1275 ofdisk iterator.
Date: Mon, 07 Dec 2009 12:05:24 +0100	[thread overview]
Message-ID: <4B1CE174.30006@gmail.com> (raw)
In-Reply-To: <20091206.224847.24234540.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]

Committed.
David Miller wrote:
> I tried to surmise other ways to do this more cleanly, such as
> resolving the path and looking for some device property inside of the
> resulting node, but there simply isn't anything we can check for.
>
>   
If you find a cleaner way we can commit it later. I was thinking of
resolving path to hardware one and then querying hardware directly but
it may conflict with OF. What do you think?
How much work would be needed to make ata.mod work on sparc64?
Which other drivers we would need to reasonably replace ofdisk (which
would still be available as fallback)? In dumps in addition to ide I see
protocols FP, ESP, SCSI, FAS, ISP, ULSA, SAS, SoC. ESP looks like
SBUS-only so it can be fallbacked to OF considering number of users. I
have no idea what FP,FAS, ISP, ULSA, SAS, SoC stand for and even if they
are real protocols or just some weird pathnames. As for SCSI we
definitely want it and already have scsi.mod but not the encapsulator of
SCSI commands

-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

  reply	other threads:[~2009-12-07 11:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  6:48 [PATCH]: Fix CDROM skipping in ieee1275 ofdisk iterator David Miller
2009-12-07 11:05 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2009-12-07 11:21   ` David Miller
2009-12-07 11:52     ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 19:49       ` David Miller

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=4B1CE174.30006@gmail.com \
    --to=phcoder@gmail.com \
    --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.