Re: T1E1 cards

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Oct 26, 2009 at 9:50 AM, Bob Beers <bob.beers@xxxxxxxxx> wrote:
> On Fri, Oct 23, 2009 at 6:17 PM, Greg KH <greg@xxxxxxxxx> wrote:
>> On Fri, Oct 23, 2009 at 01:08:49PM -0400, Bob Beers wrote:
> <snip>
>>> 2 - What is the proper way to create the upper devices as hdlcX
>>>  vs. ethX?
>>
>> The driver should do this for you.
>
> I am interested in seeing if I can make the necessary changes to the driver code
>  to have this happen, but maybe this belongs in a different forum now?
>

Greg,

 How do I move forward with this path -- fixing the driver?

I have created a script[1] and call it in an
/etc/udev/rules.d/10-local.rules, but
 now the ether interfaces and the hdlc interfaces are created at almost the
 same time, and it seems like a real mess to sort out:

# ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: pmcc4-0: <> mtu 0 qdisc noop
    link/void
3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:80:82:70:f8:9e brd ff:ff:ff:ff:ff:ff
4: eth1: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 32
    link/rawhdlc
    inet 192.168.10.47/24 brd 192.168.10.255 scope global eth1
5: eth2: <POINTOPOINT,NOARP> mtu 1500 qdisc noop qlen 32
    link/rawhdlc
6: eth3: <POINTOPOINT,NOARP> mtu 1500 qdisc noop qlen 32
    link/rawhdlc
7: eth4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:80:82:70:f8:9f brd ff:ff:ff:ff:ff:ff
8: eth5: <POINTOPOINT,NOARP> mtu 1500 qdisc noop qlen 32
    link/rawhdlc
9: eth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:80:82:70:f8:a0 brd ff:ff:ff:ff:ff:ff
10: eth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:80:82:70:f8:a1 brd ff:ff:ff:ff:ff:ff

I tried changing my local.rules file to 70-local.rules but,
 of course, the order that the interfaces appear is not reliable.

Shall I start a thread on net-dev, for advice on fixing the driver?

Thanks for any advice,

-Bob Beers

[1]
-------------------
# cat /etc/sysconfig/network-scripts/pmcinit.sh
#!/bin/sh

/sbin/modprobe pmcc4
for i in 0 1 2 3; do
        /sbin/pmcc4cfg port set -p$i -c0 -m T1_ESF
        /sbin/pmcc4cfg chan create -p$i -n$i
        /sbin/pmcc4cfg chan set -t RXTX -m HDLC_FCS16 -o 0-23 -n$i
done
-------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux DVB]     [Asterisk Internet PBX]     [DCCP]     [Netdev]     [X.org]     [Util Linux NG]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux