mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Karsten Keil <kkeil@suse.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: David Miller <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, sfr@canb.auug.org.au,
	linuxppc-dev@ozlabs.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, kkeil@suse.de
Subject: Re: mISDN still breaking the allmodconfig build...
Date: Mon, 28 Jul 2008 10:40:24 +0200	[thread overview]
Message-ID: <20080728084024.GA23465@pingi.kke.suse.de> (raw)
In-Reply-To: <7949EA87-4340-4353-AFC9-79A718B95DF0@holtmann.org>

Hi Marcel,
On Mon, Jul 28, 2008 at 03:13:21AM +0200, Marcel Holtmann wrote:
> Hi Dave,
> 
> >>>More fallout from the premature mISDN driver merge:
> >>>
> >>>drivers/isdn/hardware/mISDN/hfcmulti.c:5255:2: error: #error "not
> >>>running on big endian machines now"
> >>
> >>is that only the HFC driver or the whole mISDN stack?
> >>
> >>I know that the two old ISDN stacks where really bad on big endian,
> >>but my assumption was that we did sort this out in the end.
> >
> >One of the two mISDN drivers uses the deprecated virt_to_bus()
> >interface for handling DMA addresses (that doesn't even work on many
> >x86 systems these days) and the other mISDN driver gives the above
> >big-endian compile time error.
> >
> >In short, this driver was not ready for merging at all.
> 
> I am not defending it and agree that this driver should have had at  
> least one test run in linux-next.

Yes my fault, sorry.

> However mISDN is a whole ISDN stack.  
> So does mISDN has an issue too or do we only have a really broken  
> driver. Karsten?

Yes this is only a issue of the hardware layer not of the stack.

OK the driver are based on the old drivers already in HiSax and for
virt_to_bus() I never got a complain before and yes I already have some patches
to solve the endian issues in the HFC driver, but it was not finaly
confirmed, that all this work now on big endian systems and my PPC system
unfortunately died some time ago, so I did leave it as it is, but with
the wrong option, instead to mark it X86 only I let it break. 

On the other side this remained me to check the big endian thing again ;-)

-- 
Karsten Keil
SuSE Labs
ISDN and VOIP development
SUSE LINUX Products GmbH, Maxfeldstr.5 90409 Nuernberg, GF: Markus Rex, HRB 16746 (AG Nuernberg)

  reply	other threads:[~2008-07-28  8:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28  0:02 David Miller
2008-07-28  0:13 ` Benjamin Herrenschmidt
2008-07-28  0:48   ` Sean MacLennan
2008-07-28  9:20     ` Alan Cox
2008-07-28 11:14       ` Karsten Keil
2008-07-28  1:03 ` Marcel Holtmann
2008-07-28  1:07   ` David Miller
2008-07-28  1:13     ` Marcel Holtmann
2008-07-28  8:40       ` Karsten Keil [this message]
2008-07-28 12:49         ` Sinan Akman
2008-08-04 12:56           ` Karsten Keil
2008-07-28  1:57     ` Mikael Pettersson
2008-07-28 10:26     ` Karsten Keil
2008-07-28 10:50   ` Benjamin Herrenschmidt

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=20080728084024.GA23465@pingi.kke.suse.de \
    --to=kkeil@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=marcel@holtmann.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®