On Tue, 1 Dec 1998, Mark Ridley wrote:
> Does anyone know if there is support for the SunISDN hardware in a
> SPARCstation LX, for Linux?
>
It is currently in early alpha state. Attached is a mail from Brent
Baccala ([EMAIL PROTECTED]) who developed that stuff about how to
get it running. For more information i suggest contacting him directly.
> Kind regards.
> --
> Mark Ridley
> [EMAIL PROTECTED]
>
Ciao
-Fritz
--
Fritz Elfert phone: +49 931 281122
Wuerzburg/Germany email: [EMAIL PROTECTED]
---------------------------------------------------------------------------
From [EMAIL PROTECTED] Tue Dec 1 21:21:43 1998
Date: Tue, 17 Nov 1998 00:31:40 -0500 (EST)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Fwd: SPARC ISDN code
This seemed like it got lost the first time I sent it (about a week ago)
------ Forwarded message ------
From: [EMAIL PROTECTED]
Subject: SPARC ISDN code
Date: Wed, 11 Nov 1998 01:29:43 -0500 (EST)
To: [EMAIL PROTECTED]
Xavier -
OK, I owe you an email explaining what's going on with this. I'm
cc'ing this to [EMAIL PROTECTED], since they deserve to
know what's going on with my first Linux/SPARC ISDN alpha tester. I
read the list, so you can post any problems directly to it and I'll
follow up. If you want to subscribe, ask [EMAIL PROTECTED]
Most of the traffic on this list relates to the German CVS tree, which
I don't really use (see the end of this email for an explaination).
I pushed the DBRI ISDN code, in its current form, up to
vger.rutgers.edu early Monday morning. You can extract it from the
CVS tree and build it. Turn on ISDN, HiSax, EURO/DSS1 (I guess that's
right for France), and the DBRI driver. If you're talking PPP across
the link, you'll need to turn on the "Synchronous PPP" option, but
I've never tested that - I'm using straight HDLC right now. Build it
all into the kernel - I haven't tested it as a module yet, either.
When you boot the kernel, you should see a bunch of messages
culminating in something like "HiSax: 2 channels added". If not, then
send me the kernel messages log and a tar of /proc/openprom. I'll try
to dope it out.
Once you get that far, you'll need to download and compile the isdn4l
utilities package; try ftp://ftp.franken.de/pub/isdn4linux/v2.1/
(there's a newer version in the oldhades.think.de CVS tree, and there
is anonymous access to it, but I'm still using the FTP site's version
and it works fine).
In /dev, create:
char 45, 64 isdnctrl0
char 45, 255 isdninfo
isdnctrl symlink -> isdnctrl0
Key commands:
hisaxctrl HiSax 1 0x3ff
hisaxctrl HiSax 11 0x3ff
hisaxctrl HiSax 13 0x3ff
These three commands turn on all the debugging for the driver. After
you've run them, do something like "cat /dev/isdnctrl > log &", but be
aware that I've found bugs in the debugging code itself that can crash
the machine, so you might want to experiment with this.
isdnctrl addif isdn0
isdnctrl eaz isdn0 (your phone number here)
isdnctrl addphone isdn0 out (target phone number here)
isdnctrl l2_prot isdn0 hdlc
isdnctrl encap isdn0 ("cisco-h" or "syncppp")
ifconfig isdn0 (whatever)
And then try to ping across the interface. It should autodial. If it
doesn't, you can try "isdnctrl dial isdn0".
Now for the bad news: the version of the ISDN code in the vger tree is
old, because it's a 2.1 kernel and the Germans that are the main force
behind ISDN develop for a 2.0 kernel. I haven't even be able to get
their 2.0 tree to build on sparc, at all (it's not ISDN, it's the rest
of the tree that's a problem). However, Karsten Kiel, the main guy
for the so-called "passive" HiSax driver (what we're using, as opposed
to an "active" card that has all its smarts on the card's firmware),
assures me that they will bring 2.1 up to date and push it up to vger
in the next week or so.
Unfortunately, I've got to give my ISDN switch back tomorrow, since
the company needs it for it's real purpose that they bought it for
(teaching), so it'll be about two weeks before I can start doing much
with this again.
And frankly, I need the break. This code is a pain in the *!*$#.
If you can get a second machine (best another SPARC) to plug into the
ISDN machine via their serial ports, you can use gdb on the one to halt
the kernel on the other and do a source-level debug, just like a regular
program. (well, kinda) This is strictly optional; only if your ambition
is to become a Linux kernel hacker, but very useful if you have ideas about
getting your hands dirty in the kernel.
Try what I've outlined in this email. Let me know if anything is
confusing, or if it just doesn't work (remember, I've never tried this
with the SBUS card before; only the build-in DBRI on a SparcStation
20). Keep us posted on your progress, OK?
Merci.
--
-bwb
Brent Baccala
[EMAIL PROTECTED]