From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Alexey Zaytsev <alexey.zaytsev@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk, netdev@vger.kernel.org,
Michael Jones <mlj28@cam.ac.uk>, Krzysztof Halasa <khc@pm.waw.pl>
Subject: Re: [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS
Date: Tue, 08 May 2007 10:55:15 +0200 [thread overview]
Message-ID: <46403AF3.9000300@wpkg.org> (raw)
In-Reply-To: <f19298770705080148u70638ac2ue87241382681088@mail.gmail.com>
Alexey Zaytsev schrieb:
> On 5/8/07, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
>> Michael Jones wrote:
>>
>> >> +#ifndef __ARMEB__
>> >> +#warning Little endian mode not supported
>> >> +#endif
>> >
>> > Personally I'm less fussed about WAN / LE support. Anyone with any
>> > sense will run ixp4xx boards doing such a specialised network
>> > operation as BE. Also, NSLU2-Linux can't test this functionality with
>> > our LE setup as we don't have this hardware on-board. You may just
>> > want to declare a depends on ARMEB in Kconfig (with or without OR
>> > (ARM || BROKEN) ) and have done with it - it's up to you.
>>
>> Christian Hohnstaedt's work did support LE though.
>>
>> Not all ixp4xx boards are by definition "doing such a specialised
>> network operation".
>>
>
> I was always curious, why do people want to run ixp4xx in LE mode? What
> are the benefits that overweight the obvious performance degradation?
I guess the main reason, at least for me, is that there is only one
distro that properly supports LE ARM: Debian.
It greatly simplifies management/administration of a higher number of
devices, given the fact that Debian also supports other architectures
(not just x86/64, sometimes PPC, like most distros do).
Not always network performance is to most important factor.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2007-05-08 8:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 8:29 [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS Tomasz Chmielewski
2007-05-08 8:48 ` Alexey Zaytsev
2007-05-08 8:54 ` Michael-Luke Jones
2007-05-09 5:20 ` Why run ixp4xx LE? (Was: [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS) Rod Whitby
2007-05-08 8:55 ` Tomasz Chmielewski [this message]
2007-05-08 13:44 ` [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS Gordon Farquharson
2007-05-08 15:28 ` Krzysztof Halasa
2007-05-08 15:52 ` Lennert Buytenhek
2007-05-08 17:20 ` Krzysztof Halasa
2007-05-08 17:31 ` Tomasz Chmielewski
2007-05-08 17:51 ` Krzysztof Halasa
2007-05-09 8:58 ` Marcus Better
2007-05-09 9:12 ` Koen Kooi
2007-05-09 9:21 ` Lennert Buytenhek
2007-05-09 9:35 ` Marcus Better
2007-05-09 11:04 ` Lennert Buytenhek
2007-05-09 14:22 ` David Acker
2007-05-09 14:45 ` Michael-Luke Jones
2007-05-15 21:20 ` Lennert Buytenhek
2007-05-08 16:34 ` Krzysztof Halasa
2007-05-16 7:13 ` Christoph Hellwig
2007-05-16 7:35 ` Michael-Luke Jones
2007-05-16 9:41 ` Lennert Buytenhek
2007-05-16 10:20 ` Michael-Luke Jones
2007-05-16 10:46 ` Rod Whitby
2007-05-16 10:56 ` Lennert Buytenhek
2007-05-16 11:35 ` Rod Whitby
2007-05-16 12:00 ` Lennert Buytenhek
2007-05-16 14:58 ` Krzysztof Halasa
2007-05-16 14:44 ` Krzysztof Halasa
-- strict thread matches above, loose matches on Subject: below --
2007-05-09 10:58 Tomasz Chmielewski
2007-05-09 10:35 Mikael Pettersson
2007-05-09 11:07 ` Lennert Buytenhek
2007-05-08 8:26 Mikael Pettersson
2007-05-08 8:35 ` Michael-Luke Jones
2007-05-06 23:46 [PATCH 0/3] Intel IXP4xx network drivers Krzysztof Halasa
2007-05-07 0:07 ` [PATCH 3/3] " Krzysztof Halasa
2007-05-07 12:59 ` Michael-Luke Jones
2007-05-07 17:12 ` Krzysztof Halasa
2007-05-07 18:14 ` Michael-Luke Jones
2007-05-07 19:57 ` Krzysztof Halasa
2007-05-08 1:19 ` [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS Krzysztof Halasa
2007-05-08 5:28 ` Jeff Garzik
2007-05-08 7:22 ` Michael-Luke Jones
2007-05-08 11:37 ` Lennert Buytenhek
2007-05-08 14:31 ` Krzysztof Halasa
2007-05-08 14:53 ` Lennert Buytenhek
2007-05-08 17:17 ` Krzysztof Halasa
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=46403AF3.9000300@wpkg.org \
--to=mangoo@wpkg.org \
--cc=alexey.zaytsev@gmail.com \
--cc=khc@pm.waw.pl \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mlj28@cam.ac.uk \
--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).