Le Wednesday 12 August 2009 10:37:04 Alexander Clouter, vous avez écrit : > Florian Fainelli <florian@xxxxxxxxxxx> 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: https://dev.openwrt.org/browser/trunk/target/linux/ar7/patches-2.6.30/500-serial_kludge.patch 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 Email: florian@xxxxxxxxxxx Web: http://openwrt.org IRC: [florian] on irc.freenode.net -------------------------------
