From: Robert <kxroberto@googlemail.com>
To: grub-devel@gnu.org
Subject: Re: [FEATURE REQUEST] firewire IEEE 1394 (ohci) module
Date: Mon, 14 Nov 2011 13:03:18 +0100 [thread overview]
Message-ID: <j9r01r$2qe$1@dough.gmane.org> (raw)
In-Reply-To: <4EC05F17.8070108@gmail.com>
Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> 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.
the FiWi HD here has USB here too. Yet via USB the usable HD speed
is 2x .. 4x slower on large file transfer, and it seems even
slower on many small files.
A HD on Firewire here is quite as fast as an internal one - seen
on two laptops. So via Firewire its feels really usable, while on
USB its half way to Knoppix ..
(as far as Linux is concerned, currently I help me using FiWi by
loading the Linux kernel&initrd from another device, which needs
special updates etc.)
next prev parent reply other threads:[~2011-11-14 12:03 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
2011-11-14 12:03 ` Robert [this message]
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='j9r01r$2qe$1@dough.gmane.org' \
--to=kxroberto@googlemail.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).