mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Kristian Høgsberg" <krh@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/4] New firewire stack - updated patches
Date: Wed, 20 Dec 2006 21:34:19 +0100	[thread overview]
Message-ID: <45899E4B.2060401@s5r6.in-berlin.de> (raw)
In-Reply-To: <45898785.4000209@s5r6.in-berlin.de>

I wrote:
> Kristian Høgsberg wrote:
[eth1394]
>> The only thing I've ever heard people say about it is that it's
>> annoying because it screws up their network interface ordering.
> 
> Yeah, the same way hot-pluggable SCSI devices screw up device naming of

(I forgot to complete the post.) ... fixed SCSI devices and among
themselves. That's old and continues to become apparent with more and
more types of hardware. The solution is old too; distributors should be
aware of it.

That said, the way how eth1394 is married with ieee1394 could stand
improvement. There should be an option (and it should be the default) to
let eth1394 load its ROM entries == don't automatically modprobe eth1394
as soon as the low level set up a host adapter.
-- 
Stefan Richter
-=====-=-==- ==-- =-=--
http://arcgraph.de/sr/

  parent reply	other threads:[~2006-12-20 20:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20  0:58 Kristian Høgsberg
2006-12-20 10:42 ` Stefan Richter
2006-12-20 17:35   ` Kristian Høgsberg
2006-12-20 18:57     ` Stefan Richter
2006-12-20 20:06       ` Kristian Høgsberg
2006-12-20 21:52         ` Stefan Richter
2006-12-20 23:01           ` Stefan Richter
2006-12-20 20:34       ` Stefan Richter [this message]
2006-12-20 15:29 ` Pieter Palmers
2006-12-20 18:39   ` Kristian Høgsberg
2006-12-21 23:03 ` Stefan Richter
2006-12-21 11:47 Duncan Beadnell

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=45899E4B.2060401@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=krh@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®