Re: I have two 1394 port in my computer, why did I get only one eth1394 interface?

[Stefan Richter <stefanr@s5r6.in-berlin.de>]

(added Cc: linux1394-user)

lepton wrote:
>    My computer has two 1394 port, one is in the front panel, and another
> is in the back. I found with linux 1394 ethernet support, I only get one
> ethernet device named eth1.
>    After read code, I found author says "This is where we add all of
> our ethernet * devices. One for each host."
>    Then my question is:
>    1. Is it possible to use every 1394 port as a ethernet device?

Yes.

>    2. If not, which port should I plug my firewire line into?

Any one port.  Note though that front panel connectors may have a
slightly reduced signal quality due to the onboard pin headers, jumper
cable, and front panel board traces.

>    3. If I must plug my firewire line in some port, can I change the
> default port to use?

Not necessary.

To explain this further:  Each FireWire controller comes in two parts
(which are sometimes integrated on a single chip though):  The link
layer controller and the PHY(sical bus interface).  The PHY may have
several ports, but all of these ports belong to the same FireWire bus.
The PHY not only connect the link layer controller with each port, it
also acts as hub/repeater between those ports.

There are a few FireWire controller cards which come with two, three, or
even four link layer controllers on the same card.  These cards too have
one PHY per link layer controller, i.e. two/ three/ four PHYs on the
card.  These cards appear to the ieee1394 drivers like multiple cards
(and multiple FireWire buses), hence will give you multiple eth1394
network interfaces just like multiple separate cards will do.

So, you get as many eth1394 interfaces as there are link layer
controllers.  You can check the number of present link layer controllers
by lspci.
-- 
Stefan Richter
-=====-=-=== =--- -==-=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/