From: Matthias Thomae <thomae@ei.tum.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] cmtp, capidrv and kernel 2.6
Date: Tue, 03 Feb 2004 10:09:29 +0100 [thread overview]
Message-ID: <401F6549.2020400@ei.tum.de> (raw)
In-Reply-To: <1075562378.2720.8.camel@pegasus>
Hi Marcel,
Marcel Holtmann wrote:
>>could anyone give a hint what changes are necessary from kernel 2.4.X to
>>2.6.X to get an isdn dialup setup via cmtp and capidrv (i4l)?
>
>
> the I4L and CAPI ISDN subsystem of 2.6 must be resynced and I hope
> Karsten Keil is doing this very soon. For now apply the i4l-t9bk22 patch
> and try again.
Thank you for your hint, I tried again and it seems to work now :)))
>>- cmtp and kernelcapi are loaded and connecting to an AP-X works
>
> You have to load capi.ko by hand and mount the capifs.
Ok, that's one that I missed.
>>- capidrv isn't loaded automatically any more
>
> Can't tell you why, but simply load it :)
Well, I had to learn that there is the directory /etc/modprobe.d first...
>>- "/etc/init.d/isdnutils start" complains about /dev/isdnctrl (because
>>of missing capidrv?)
>
> Maybe the scripts need a little bit 2.6 cleanup.
Don't think so, that was due to the missing capidrv.
>>I use debian/unstable with the latest isdn and capi packages (3.3-7).
>
> With the i4l-t9bk22 the CAPI part should work perfect.
Seems to :)
>>Do I have to modify the module loading definitions in /etc/modutils?
>
> Not that I know of.
Well, I copied them to the new /etc/modprobe.d, e.g.:
alias char-major-43 capidrv
alias char-major-44 capidrv
alias char-major-45 capidrv
>>Does pppdcapiplugin work without additional kernel patches?
>
> No.
But it seems to with the i4l-t9bk22 patch :)
Cheerio
Matthias
next prev parent reply other threads:[~2004-02-03 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 9:40 [Bluez-users] cmtp, capidrv and kernel 2.6 Matthias Thomae
2004-01-31 15:19 ` Marcel Holtmann
2004-02-03 9:09 ` Matthias Thomae [this message]
2004-02-03 11:37 ` Marcel Holtmann
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=401F6549.2020400@ei.tum.de \
--to=thomae@ei.tum.de \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.