From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [FEATURE REQUEST] firewire IEEE 1394 (ohci) module
Date: Mon, 14 Nov 2011 01:21:43 +0100 [thread overview]
Message-ID: <4EC05F17.8070108@gmail.com> (raw)
In-Reply-To: <j9pld1$70s$1@dough.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
On 14.11.2011 00:55, Robert wrote:
> I'd like to boot from Grub into Firewire IEEE 1394 (ohci) ;-)
>
That's one thing we don't risk having soon. Few people even have such
hardware (my laptop has no firewire connector at all). Some of my test
machines have it but I have no firewire HDD. Even fewer of these people
have required skills (it requires someone who had a similar experience
like Aleš or me). And even less have motivation. Additionally since most
of external HDDs supporting firewire also support USB, it seems pretty
pointless. So it will probably never happen.
Of course, you can back up your feature request with work (a patch, make
sure you don't include any license-incompatible code, consult before
including any third-party code) or money (by sponsoring hardware and
putting a bounty).
> Robert
>
>
> PS: USB UHCI modules do already exist, but they seem to not work
> properly (v1.98)
That's old. USB has evolved a lot since then.
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-11-14 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 23:55 [FEATURE REQUEST] firewire IEEE 1394 (ohci) module Robert
2011-11-14 0:21 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-11-14 12:03 ` Robert
2011-11-14 12:13 ` Robert
2011-11-14 12:20 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-14 12:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4EC05F17.8070108@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).