From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: sfr@canb.auug.org.au, kkeil@suse.de,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
David Miller <davem@davemloft.net>
Subject: Re: mISDN still breaking the allmodconfig build...
Date: Mon, 28 Jul 2008 20:50:53 +1000 [thread overview]
Message-ID: <1217242253.11188.197.camel@pasglop> (raw)
In-Reply-To: <93120C4B-D2F4-4479-806B-2141AC3DC607@holtmann.org>
On Mon, 2008-07-28 at 03:03 +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.
Well, I got it working well enough (the old one) on a ppc405 about 5 or
6 years ago... It did require some endian & dma mapping fixing, iirc, in
the hisax pci driver, but nothing very tricky.
What bugs me is that we -fixed- at least some of these things in the old
stack, up to the point where I could use it reliably in some commercial
products, and now we are merging a new stack which, in that area, is a
clear regression over the old code.
One basic premise to me for replacing a whole stack with a new one is
that the new one should be -at-least- as good as the old one in all
areas, and those (virt_to_bus and endianness) are pretty major.
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: David Miller <davem@davemloft.net>,
sfr@canb.auug.org.au, kkeil@suse.de,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org
Subject: Re: mISDN still breaking the allmodconfig build...
Date: Mon, 28 Jul 2008 20:50:53 +1000 [thread overview]
Message-ID: <1217242253.11188.197.camel@pasglop> (raw)
In-Reply-To: <93120C4B-D2F4-4479-806B-2141AC3DC607@holtmann.org>
On Mon, 2008-07-28 at 03:03 +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.
Well, I got it working well enough (the old one) on a ppc405 about 5 or
6 years ago... It did require some endian & dma mapping fixing, iirc, in
the hisax pci driver, but nothing very tricky.
What bugs me is that we -fixed- at least some of these things in the old
stack, up to the point where I could use it reliably in some commercial
products, and now we are merging a new stack which, in that area, is a
clear regression over the old code.
One basic premise to me for replacing a whole stack with a new one is
that the new one should be -at-least- as good as the old one in all
areas, and those (virt_to_bus and endianness) are pretty major.
Ben.
next prev parent reply other threads:[~2008-07-28 10:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 0:02 mISDN still breaking the allmodconfig build David Miller
2008-07-28 0:02 ` David Miller
2008-07-28 0:13 ` Benjamin Herrenschmidt
2008-07-28 0:13 ` Benjamin Herrenschmidt
2008-07-28 0:48 ` Sean MacLennan
2008-07-28 0:48 ` Sean MacLennan
2008-07-28 9:20 ` Alan Cox
2008-07-28 9:20 ` Alan Cox
2008-07-28 11:14 ` Karsten Keil
2008-07-28 11:14 ` Karsten Keil
2008-07-28 1:03 ` Marcel Holtmann
2008-07-28 1:03 ` Marcel Holtmann
2008-07-28 1:07 ` David Miller
2008-07-28 1:07 ` David Miller
2008-07-28 1:13 ` Marcel Holtmann
2008-07-28 1:13 ` Marcel Holtmann
2008-07-28 8:40 ` Karsten Keil
2008-07-28 8:40 ` Karsten Keil
2008-07-28 12:49 ` Sinan Akman
2008-07-28 12:49 ` Sinan Akman
2008-08-04 12:56 ` Karsten Keil
2008-08-04 12:56 ` Karsten Keil
2008-07-28 1:57 ` Mikael Pettersson
2008-07-28 1:57 ` Mikael Pettersson
2008-07-28 10:26 ` Karsten Keil
2008-07-28 10:26 ` Karsten Keil
2008-07-28 10:50 ` Benjamin Herrenschmidt [this message]
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=1217242253.11188.197.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kkeil@suse.de \
--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 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.