Again, ipppd has one kernel connection per channel in a MPPP
setting, so we should keep track in isdn_net_dev.

Dialing happens per channel / isdn_net_dev, so the move the
corresponding members there.

This is the first step of a long series moving members between
isdn_net_local and isdn_net_dev.

Today, a one-to-one relationship between these both structures exist, so
it does not really matter where the members live. However, the goal
is to get a correspondence like

net_device -> isdn_net_local -> master isdn_net_device
                                           |
                                slave  isdn_net_device
                                           |
                                slave  isdn_net_device

where more than one isdn_net_device can exist per actual net_device,
due to channel bundling.

X25 needs notification if an interface is brought up or down, and
ethernet over ISDN creates a fake MAC address at open time, so put this
into appropriate callbacks as well.

The ->init() callback can be used for calling ether_setup() in case
of encapsulation "ISDN over ethernet", for the other cases it does not
make sense anyway.

X25 needs notification when encapsulation is set to X25 and when
it is changed to something else again, so let's have some callbacks
for init/cleanup.

Use a struct of methods and parameters to describe the
different kinds of network interfaces supported by isdn_net.c
and friends.

PPP wants callbacks at the time a connection between ISDN channel
and network interface is established, i.e. before dialing to
avoid dialing when no ipppd is present, so use generic
bind/unbind callbacks.

The method to find out if an incoming call is addressed to
any of the ISDN network interfaces is horrible. A bit of splitting
and dropping the swap channels if exclusive logic makes it a bit
better at least.

The same information is present as (->isdn_slot >= 0), so don't
duplicate it (and risk it getting out of sync)

No need to duplicate that function privately.

When using exclusive mode, we already reserved our channel
at the time that mode was set, so no need to get a free channel
in this case.

Also, indent cleanups to isdn_net_start_xmit().

We will need the index of the channel we reserved later, so override
the meaning of ->exclusive.

Put the test for lp->flags & ISDN_NET_CONNECTED into an inline
function called isdn_net_bound(), which more accurately names what
we are testing for, i.e. the interface being bound to a hardware
ISDN channel, which however is not necessarily online yet.

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.isdn

into home.transmeta.com:/home/torvalds/v2.5/linux

* fix eeprom accesses
* fix tx desc overflow
* fix tx timeout bug
* add sis963 support

(contributed by Edward Peng @ D-Link)

(contributed by Edward Peng @ D-Link)

(contributed by Edward Peng @ D-Link, cleaned up by me)

conditionally include crc32.h, ethtool.h, mii.h, and compat.h
if built outside the stock 2.4.x kernel.

Conditionally enabled when out-of-tree, but open source, crypto lib
is present.

into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5

a directory pattern. Clean directories _first_, then files.

Again, instead of a switch statement, just use a callback.

Again, instead of a switch statement, just use a callback.

Use the same form for the already existing PPP / X.25 receive functions
as for all the other ones, + small fixes.

Another step in splitting isdn_net_receive into type specific functions.

Another step in splitting isdn_net_receive into type specific functions.

Another step in splitting isdn_net_receive into type specific functions.

Another step in splitting isdn_net_receive into type specific functions.

First step in splitting isdn_net_receive into type specific functions.

Break syncPPP and UI HDLC specific parts out of isdn_net_header()
and move it to more appropriate places.

Break the CISCO specific part out of the generic isdn_net_header()
and move it to the CISCO code.

isdn_net handles all kind of interfaces, e.g. raw IP, ethernet over ISDN,
PPP - this is a cleanup making the setup of a net_device specific to the
type of interface.