netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	isdn4linux@listserv.isdn4linux.de
Subject: Re: ISDN testing
Date: Sun, 20 Apr 2008 21:43:57 -0400	[thread overview]
Message-ID: <480BF15D.2090100@garzik.org> (raw)
In-Reply-To: <200804210205.38891.elendil@planet.nl>

Frans Pop wrote:
> (Dropping private CCs.)
> 
> Jeff Garzik wrote:
>> - "isn't ISDN dead?"  Apparently, no it's not :)
>>
>> - "don't waste your time, drop these drivers and get mISDN into the
>>   kernel instead" -- based on discussion it does sound like mISDN should
>>   get into the kernel.  Until these drivers are dropped, however, my
>>   patches remain appropriate.
>>
>> And in case people are curious, #isdn-pci isn't ready for upstream yet
>> for two main reasons: (1) two drivers remain unconverted, and (2) none
>> of the changes have been tested, even once.
> 
> I have three different ISDN cards. However, since I've had ADSL since about 
> 3 years (on top of ISDN), I don't actually use it anymore.
> 
> I could be persuaded to do some testing though, or to donate some or all of 
> my cards for that purpose.
> 
> For testing I'd at least need somewhere to connect to, preferably in NL.
> I have no idea if I could still connect to my previous provider using ISDN. 
> The account was transferred to a different provider about 2 years ago, but 
> the mail accounts with the old provider are still active.
> 
> The cards I have are:
> - Teles 16.3 ISA -- worked way back when with Debian Woody
> - ITK ix1-micro 2.1 ISA
> - Eicon Diva 2.01 PCI
> 
> I also have a test box I can put them in :-)
> 
> Looks like I can still at least successfully load the hisax driver with 
> 2.6.18 for the Teles card. For the last two I'm not sure if I ever had them 
> working with Linux (or even if I tried).

Honestly, a module-load test on real hardware can give us some useful 
information, even if it's not connected to anything.

My changes are primarily in the probe-the-hardware area, so successfully 
making it past that new code would indeed be a useful data point.

Check out the kernel found in 'isdn-pci' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git

Any help is certainly appreciated!

	Jeff





  reply	other threads:[~2008-04-21  1:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-20 22:39 [git patches] ISDN cleanups (modularization prep) Jeff Garzik
2008-04-21  0:05 ` ISDN testing (was: [git patches] ISDN cleanups (modularization prep)) Frans Pop
2008-04-21  1:43   ` Jeff Garzik [this message]
2008-04-21 13:36     ` ISDN testing Frans Pop
2008-04-21 19:22       ` Jeff Garzik
2008-04-21 19:48         ` Andi Kleen
2008-04-25  2:39           ` Jeff Garzik
2008-04-21 20:21         ` [git patches] ISDN cleanups (modularization prep) (was: ISDN testing) Frans Pop
2008-04-25  2:46           ` [git patches] ISDN cleanups (modularization prep) Jeff Garzik
2008-04-26 19:42             ` Frans Pop
2008-04-25 16:47   ` ISDN testing (was: [git patches] ISDN cleanups (modularization prep)) Jan Engelhardt

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=480BF15D.2090100@garzik.org \
    --to=jeff@garzik.org \
    --cc=elendil@planet.nl \
    --cc=isdn4linux@listserv.isdn4linux.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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).