[Top] [All Lists]

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

To: Alexander Clouter <>
Subject: Re: AR7 runtime identification [was:- Re: [PATCH -v1] MIPS: add support for gzip/bzip2/lzma compressed kernel images]
From: Florian Fainelli <>
Date: Wed, 12 Aug 2009 11:19:44 +0200
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=domainkey-signature:received:received:sender:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=tMdjKw7SFVwt7WR9GKY3Ncj1ZgbgcTPkaot9moRrWeE=; b=UaPgiEOjSb1qCXR6vPenPrKAR1ajK4d0liOVps6LgouvosVRApkaVwhGAbEMSFbtr4 cxkbV9AaeRSbahTXH9tpSwFCLi9mSWw3LiZPV9WFX/HBYzW+AcUcvqB8qI6hMjYLdtHF qrA7gvv6CkTIzR7ACrLJVO/qLZx3Ly0AjbgSM=
Domainkey-signature: a=rsa-sha1; c=nofws;; s=gamma; h=sender:from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:message-id; b=s8JhetwAgrGEOXkMUR83zdiypXhYMmsLI65UWBsWWn8XogTJl56pnmM9R2lo0Epyus IQXSQvVpACVgYx5lM0+KWWM5oQ3tvJBHL1PDBT7NiFpCwBCuXgDacC0ZRcw1H3ErFsAj bjyCWGwCkRg+2jy394adGOHcbX+rai5Haa1do=
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <>
User-agent: KMail/1.9.9
Le Wednesday 12 August 2009 10:37:04 Alexander Clouter, vous avez écrit :
> 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.

Or simply enable the workaround even for sane hardware like it is done here:
as this patch has no side effect on working hardware.

> 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.... :)
> Cheers
> --  
Cordialement, Florian Fainelli
Best regards, Florian Fainelli
IRC: [florian] on

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