From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Mon, 17 Apr 2006 17:01:24 +0100 (BST) Received: from rtsoft2.corbina.net ([85.21.88.2]:29846 "HELO mail.dev.rtsoft.ru") by ftp.linux-mips.org with SMTP id S8133415AbWDQQBN (ORCPT ); Mon, 17 Apr 2006 17:01:13 +0100 Received: (qmail 22195 invoked from network); 17 Apr 2006 20:16:20 -0000 Received: from wasted.dev.rtsoft.ru (HELO ?192.168.1.248?) (192.168.1.248) by mail.dev.rtsoft.ru with SMTP; 17 Apr 2006 20:16:20 -0000 Message-ID: <4443BE71.6090908@ru.mvista.com> Date: Mon, 17 Apr 2006 20:12:33 +0400 From: Sergei Shtylyov Organization: MontaVista Software Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.2) Gecko/20040803 X-Accept-Language: ru, en-us, en-gb MIME-Version: 1.0 To: Atsushi Nemoto CC: linux-mips@linux-mips.org Subject: Re: tx49 Ether problems References: <444291E9.2070407@ru.mvista.com> <20060417.110945.59031594.nemoto@toshiba-tops.co.jp> <444392CF.7070808@ru.mvista.com> <20060418.000918.95064811.anemo@mba.ocn.ne.jp> <4443BD39.4030200@ru.mvista.com> In-Reply-To: <4443BD39.4030200@ru.mvista.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 11141 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: sshtylyov@ru.mvista.com Precedence: bulk X-list: linux-mips Hello. Sergei Shtylyov wrote: >> On Mon, 17 Apr 2006 17:06:23 +0400, Sergei Shtylyov >> wrote: >>>> I agree with you. Then how about something like >>>> CONFIG_NE2000_RTL8019_BYTEMODE? >>> Have you looked at the patch? RTL8019 is easily detectable at >>> runtime, so the limitation is easily enforcable w/o extra Kconfig >>> option, I think >> Well, I meant something like: >> #elif defined(CONFIG_NE2000_RTL8019_BYTEMODE) >> # define DCR_VAL 0x48 >> #else >> # define DCR_VAL 0x49 >> to avoid changing #elif line every time when we want to support a new >> board with byte-mode RTL8019AS. Of course, calculating DCR_VAL at >> runtime would be much better but I'm not sure if we can do it ... > Hm, with only 3-4 known boards so far (all Toshiba RBTX49[23][78], > RBTX4925 also has the chip but I see no 2.6 support for this board), I > doubt that it's worth the effort. And the option sounds a bit "too > specific", IMO. :-) Especially given the fact that it can't be attributed to RTL8019 only. Historically, there was CONFIG_NE2000_8BIT option but it's been eliminated long ago. Maybe it's worth reviving it indeed... >> --- >> Atsushi Nemoto WBR, Sergei