[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121122213950.GA8873@electric-eye.fr.zoreil.com>
Date: Thu, 22 Nov 2012 22:39:50 +0100
From: Francois Romieu <romieu@...zoreil.com>
To: Jeff Garzik <jgarzik@...ox.com>
Cc: David Miller <davem@...emloft.net>, dwmw2@...radead.org,
jasowang@...hat.com, netdev@...r.kernel.org, slacky@...apnet.it,
rggjan@...il.com, gilboad@...il.com,
Hayes Wang <hayeswang@...ltek.com>
Subject: Re: [PATCH] 8139cp: set ring address after enabling C+ mode
Jeff Garzik <jgarzik@...ox.com> :
> On 11/21/2012 11:39 PM, David Miller wrote:
> >From: Jeff Garzik <jgarzik@...ox.com>
> >Date: Wed, 21 Nov 2012 22:47:39 -0500
> >
> >>State A: pre-b01af457, known working
> >>State B: b01af457, known broken
> >
> >State A is also known buggy on the largest consumer of this driver,
> >the emulated hardware.
>
> >Please evaluate this realistically.
>
> If the simulator fails to match the hardware, that is a simulator bug.
Yes.
> It is disappointing to work around someone else's software bug in
> the kernel.
Yes. :o/
I like David Woodhouse's C (attached patch) since 1) Realtek does
not seem to care about oldies 2) the emulation will not be fixed in a
decent timeframe 3) real 8139cp users care.
It would be nice if gilboad could give it a try (users Cced).
Btw David W., could consider adding artificial delays between the writes
and see if / when things start to fail (CpCmd write in cp_start_hw is an
unflushed posted write for instance).
--
Ueimor
Download attachment "8139cp.patch.gz" of type "application/x-gzip" (934 bytes)
Powered by blists - more mailing lists