From: James Ketrenos <jketreno@linux.intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jeff Garzik <jeff@garzik.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Zhu Yi <yi.zhu@intel.com>
Subject: Re: [PATCH] Add iwlwifi wireless drivers [part 2/2]
Date: Mon, 21 May 2007 09:48:30 -0700 [thread overview]
Message-ID: <4651CD5E.10801@linux.intel.com> (raw)
In-Reply-To: <20070521162659.GA28901@infradead.org>
Christoph Hellwig wrote:
> On Mon, May 21, 2007 at 07:56:10AM -0700, James Ketrenos wrote:
>> Christoph Hellwig wrote:
>>> On Fri, May 18, 2007 at 02:31:54PM -0700, James Ketrenos wrote:
>>>> Alright; I'll add replacing the bitfields with bitwise access to the todo
>>>> list.
>>>>
>>>> Are you OK with us marking the driver as not working on big endian for
>>>> now and getting this one fixed over time?
>>> Given that Intel still hasn't fixed the older ipw2X00 drivers for big
>>> endian despite clong-time onstant prodding I'm dead set against this.
>> Really? Long time constant prodding?
>>
>> I'll admit I'm not CC:'d on every email regarding the ipw2100 and ipw2200,
>> so if I missed a long-time and constant thread, please forward it my way.
>> Searching Google for 'ipw endian' (and several other searches) found a
>> reference to a fix for an endian issue when it was raised for the ipw2200.
>
> Just from my outbox I have a thread in August 2006 where I tell Zhu Yi
> to fix the endianess problems instead of masking them, and even offer
> testing on big endian when Intel sends me hardware. Despite that this
> got completely ignored and resubmitted in december, where I replied again.
> And probably quite a few more I haven't caught.
Ok, first, you said 'ipw2x00' Which is false. The ipw2200 does work on big endian. We have worked to enable it. You also said merging w/out fixing big endian leads to big endian never being fixed. Again, false (see prior email with specific references demonstrating that).
So, Please don't generalize and make false accusations.
Second, regarding your prior thread, you more or less demanded that the driver maintainer send you hardware. That isn't fair or reasonable.
If you have a bug, and users that can help resolve the bug, we'd love to work with them fix the issues. But demanding that Yi send you hardware and then making stuff up about him and the ipw2100, ipw2200, and iwlwifi projects when he doesn't is really not appropriate.
James
next prev parent reply other threads:[~2007-05-21 18:11 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 21:45 [PATCH] Add iwlwifi wireless drivers James Ketrenos
2007-05-17 1:27 ` Randy Dunlap
2007-05-17 4:28 ` James Ketrenos
2007-05-17 5:57 ` Jeff Garzik
2007-05-22 21:38 ` James Ketrenos
2007-05-18 19:01 ` James Ketrenos
2007-05-18 20:57 ` Jeff Garzik
2007-05-18 20:54 ` James Ketrenos
2007-05-18 21:06 ` Randy Dunlap
2007-05-22 18:39 ` John W. Linville
2007-05-22 18:29 ` James Ketrenos
2007-05-17 1:51 ` Michael Wu
2007-05-17 2:56 ` Jeff Garzik
2007-05-17 3:55 ` Michael Wu
2007-05-17 8:52 ` Christoph Hellwig
2007-05-22 19:16 ` James Ketrenos
2007-05-22 23:00 ` Jeff Garzik
2007-05-22 21:49 ` James Ketrenos
2007-05-22 23:41 ` Jeff Garzik
2007-05-22 22:56 ` James Ketrenos
2007-05-23 0:58 ` Jeff Garzik
2007-05-23 18:17 ` James Ketrenos
2007-05-23 19:59 ` Jeff Garzik
2007-05-23 19:30 ` James Ketrenos
2007-05-23 1:06 ` Michael Wu
2007-05-23 1:46 ` Jeff Garzik
2007-05-17 3:35 ` [PATCH] Add iwlwifi wireless drivers [part 2/2] Randy Dunlap
2007-05-17 15:03 ` Stephen Hemminger
2007-05-17 15:05 ` Stephen Hemminger
2007-05-18 7:04 ` Johannes Berg
2007-05-18 20:33 ` James Ketrenos
2007-05-18 22:05 ` Jeff Garzik
2007-05-18 21:31 ` James Ketrenos
2007-05-18 22:50 ` Jeff Garzik
2007-05-18 23:04 ` Christoph Hellwig
2007-05-21 14:56 ` James Ketrenos
2007-05-21 16:26 ` Christoph Hellwig
2007-05-21 16:48 ` James Ketrenos [this message]
2007-05-21 18:15 ` Christoph Hellwig
2007-05-21 20:12 ` Cohen, Guy
2007-05-21 21:02 ` Jeff Garzik
2007-05-21 21:10 ` Randy Dunlap
2007-05-21 21:43 ` Cohen, Guy
2007-05-21 22:15 ` Jeff Garzik
2007-05-21 21:22 ` Joerg Mayer
2007-05-21 21:46 ` Cohen, Guy
2007-05-18 22:13 ` Randy Dunlap
2007-05-18 23:05 ` [PATCH] Add iwlwifi wireless drivers Christoph Hellwig
2007-05-18 23:22 ` Michael Wu
2007-05-22 21:50 ` [PATCH v3] " James Ketrenos
2007-05-23 1:06 ` Jeff Garzik
2007-05-23 15:16 ` James Ketrenos
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=4651CD5E.10801@linux.intel.com \
--to=jketreno@linux.intel.com \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=randy.dunlap@oracle.com \
--cc=yi.zhu@intel.com \
/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).