linux-kernel - Re: Plans for mISDN?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47C2D312.60100@imap.cc>
Date:	Mon, 25 Feb 2008 15:39:14 +0100
From:	Tilman Schmidt <tilman@...p.cc>
To:	kkeil@...e.de
CC:	Simon Richter <sjr@...ian.org>, Jeff Garzik <jeff@...zik.org>,
	Greg KH <greg@...ah.com>,
	Gregory Nietsky <gregory@...worksentry.co.za>,
	linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>,
	isdn4linux@...tserv.isdn4linux.de, Sam Ravnborg <sam@...nborg.org>
Subject: Re: Plans for mISDN?

On 22.02.2008 13:04, Karsten Keil wrote:
> These design issues are fixed in the new mISDN socket branch.
> The old mISDN design was too complicated because it allow access to
> every layer and build the ISDN stack dynamically, both feature were never
> needed in practice and contain many race conditions.
> The new design only has one core module and hardware specific modules
> with a very simple interface.

Great news. I pulled your socket branch and am currently trying to
find my way through one of the two hardware drivers available there
and abstract away from the PCI card specific parts.
Is there a design document available? Or will there be some non-PCI
driver soon, perhaps even one for a USB device? That would be
immensely helpful.

Thanks,
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


Download attachment "signature.asc" of type "application/pgp-signature" (251 bytes)