mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Karsten Keil <kkeil@suse.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: kai.germaschewski@gmx.de, Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ISDN: mark as 32-bit only
Date: Mon, 2 Oct 2006 11:26:40 +0200	[thread overview]
Message-ID: <20061002092640.GA10395@pingi.kke.suse.de> (raw)
In-Reply-To: <20061001152116.GA4684@havoc.gtf.org>

On Sun, Oct 01, 2006 at 11:21:16AM -0400, Jeff Garzik wrote:
> 
> Tons of ISDN drivers cast pointers to/from 32-bit values, which just
> won't work on 64-bit.
> 

NACK.

This is no problem for ISDN only some old HW drivers may not work (for most
I do not have any hardware by myself). 
I will compile all drivers again and if here are 64 bit issues I will
disable the drivers, not ISDN.

ISDN works on 64 bits, at least with following protocols:
- transparent (audio/voice)
- X.75
- HDLC
- sync PPP

Maybe some other protocols need some 64 bit cleanup, but last time I audited
the ISDN core code for 64 bit I did not saw any problems.
My main test machines are 64 bit (and SMP) and they are running ISDN servers
for sync PPP and voice data processing on different ISDN HW and drivers
(CAPI and Hisax) without any problem.

You will see still some warnings in the CAPI code, because the capi code
has dual 64/32 bit protocol format for data packets (has 2 different pointer
areas one for 64 bit one for32 bit), but this is OK.

> Signed-off-by: Jeff Garzik <jeff@garzik.org>
> 
> diff --git a/drivers/isdn/Kconfig b/drivers/isdn/Kconfig
> index c90afee..608588f 100644
> --- a/drivers/isdn/Kconfig
> +++ b/drivers/isdn/Kconfig
> @@ -6,7 +6,7 @@ menu "ISDN subsystem"
>  
>  config ISDN
>  	tristate "ISDN support"
> -	depends on NET
> +	depends on NET && 32BIT
>  	---help---
>  	  ISDN ("Integrated Services Digital Networks", called RNIS in France)
>  	  is a special type of fully digital telephone service; it's mostly

-- 
Karsten Keil
SuSE Labs
ISDN development

  parent reply	other threads:[~2006-10-02  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-01 15:21 Jeff Garzik
2006-10-01 18:08 ` Jan Engelhardt
2006-10-02  3:54   ` Jeff Garzik
2006-10-02 20:37     ` David Miller
2006-10-02 22:04       ` Alan Cox
2006-10-01 20:53 ` Alan Cox
2006-10-01 23:47 ` Alan Cox
2006-10-02  9:31   ` Karsten Keil
2006-10-02  9:26 ` Karsten Keil [this message]
2006-10-02  9:46 ` Andi Kleen
2006-10-01 23:24 Tilman Schmidt
2006-10-02  0:10 Tilman Schmidt

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=20061002092640.GA10395@pingi.kke.suse.de \
    --to=kkeil@suse.de \
    --cc=akpm@osdl.org \
    --cc=jeff@garzik.org \
    --cc=kai.germaschewski@gmx.de \
    --cc=linux-kernel@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

Powered by JetHome