From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: T1E1 cards
Date: Fri, 23 Oct 2009 22:17:52 +0000 [thread overview]
Message-ID: <20091023221752.GA7466@kroah.com> (raw)
In-Reply-To: <4f6ba3b0910231008p3fd4481bm5807813f13ee0ad8@mail.gmail.com>
On Fri, Oct 23, 2009 at 01:08:49PM -0400, Bob Beers wrote:
> Hi list,
>
> I have a 4-port T1E1 card with this lspci output:
>
> # lspci -n -s05:08
> 05:08.0 0280: 14f1:8474 (rev 0c)
> 05:08.1 0680: 14f1:8474 (rev 0c)
> # lspci -v -s05:08
> 05:08.0 Network controller: Conexant Systems, Inc. Unknown device 8474 (rev 0c)
> Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 74
> BIST result: 00
> Memory at fe900000 (32-bit, non-prefetchable) [size=1M]
>
> 05:08.1 Bridge: Conexant Systems, Inc. Unknown device 8474 (rev 0c)
> Flags: 66MHz, medium devsel, IRQ 82
> Memory at fea00000 (32-bit, non-prefetchable) [size=1M]
>
>
> I have the (GPL, but not in-kernel) driver compiled and when I
> manually modprobe it, I get a low level device. Then I have to
> set up the ports and create channels using the card specific
> cfg utility. At this point I see new devices which I can manipulate
> with my if[up|down]-hdlc scripts. Unfortunately, they are ethX
> instead of hdlcX, but it all still works.
>
> So, finally, here are my questions:
>
> 1 - How can I get the driver to load automatically, and execute the
> cfg calls to create the low level device?
Fix the driver to have it load automatically. Do you have a pointer to
the source code for it anywhere?
> 2 - What is the proper way to create the upper devices as hdlcX
> vs. ethX?
The driver should do this for you.
> I know that I can use 'ip link set dev eth4 name hdlc0'
> or something like ifrename for renaming once they're created,
> but maybe I can change something in the driver code to have
> them start out with the right interface name.
Yes, you can, or you can write a udev rule to rename the device when it
is seen.
thanks,
greg k-h
next prev parent reply other threads:[~2009-10-23 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 17:08 T1E1 cards Bob Beers
2009-10-23 21:03 ` Bob Beers
2009-10-23 22:17 ` Greg KH [this message]
2009-10-23 22:45 ` Matthew Dharm
2009-10-26 13:29 ` Bob Beers
2009-10-26 13:50 ` Bob Beers
2009-10-26 18:25 ` Bob Beers
2009-10-26 18:34 ` Greg KH
2009-10-26 20:01 ` Bob Beers
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=20091023221752.GA7466@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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).