[Top] [All Lists]

Re: AR7 runtime identification [was:- Re: [PATCH -v1] MIPS: add support

Subject: Re: AR7 runtime identification [was:- Re: [PATCH -v1] MIPS: add support for gzip/bzip2/lzma compressed kernel images]
From: Alexander Clouter <>
Date: Wed, 12 Aug 2009 09:37:04 +0100
Original-recipient: rfc822;
References: <> <20090810101205.GW19816@chipmunk> <> <>
User-agent: tin/1.9.3-20080506 ("Dalintober") (UNIX) (Linux/2.6.26-2-sparc64-smp (sparc64))
Florian Fainelli <> wrote:
>> Le Monday 10 August 2009 12:12:05 Alexander Clouter, vous avez écrit :
>> For your information, the TNETD7300GDU is detected like this:
>> TI AR7 (TNETD7300), ID: 0x0005, Revision: 0x02
>> and the TNETD7300EZDW (ADSL 2+) is detected like this:
>> TI AR7 (TNETD7200), ID: 0x002b, Revision: 0x10 which also has the UART bug
>> and is wrongly detected as a TNETD7200.
>> I have left the WAG54G at work and will get my hands back on it tomorow.
> The bad news is that my WAG54G v2 which is also a TNEDT7300GDU has this HW 
> bug 
> too rendering the runtime detection of the bug more difficult.
Well, two options I guess.  Another Kconfig or pass something 
on the command line to the kernel.  I would opt for the latter as the 
bug does not make the machine completely unusable and if you make sure 
the workaround is disabled by default hopefully that will have the 
effect of getting people to contact you to add an extra data point.

Annoyingly I'm guess we are more interested in people who do *not* have 
the bug and we would not hear from them as a result.  Maybe if we 
proactively crippled their serial port.... :)


Alexander Clouter
.sigmonster says: Be braver -- you can't cross a chasm in two small jumps.

<Prev in Thread] Current Thread [Next in Thread>