From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8097 invoked by alias); 17 Aug 2005 16:31:10 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 7986 invoked by uid 22791); 17 Aug 2005 16:30:53 -0000 Received: from web60817.mail.yahoo.com (HELO web60817.mail.yahoo.com) (209.73.178.225) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Wed, 17 Aug 2005 16:30:53 +0000 Received: (qmail 50491 invoked by uid 60001); 17 Aug 2005 16:30:52 -0000 Message-ID: <20050817163052.50489.qmail@web60817.mail.yahoo.com> Received: from [216.101.234.182] by web60817.mail.yahoo.com via HTTP; Wed, 17 Aug 2005 09:30:51 PDT Date: Wed, 17 Aug 2005 16:31:00 -0000 From: baljeet singh To: Gary Thomas Cc: eCos Discussion In-Reply-To: <1124231208.29732.81.camel@hermes> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: [ECOS] DM9000 ethernet drivers X-SW-Source: 2005-08/txt/msg00200.txt.bz2 Gary, Thanks. Question- Where do I invoke these macros to let the system knows that the hardware driver is in place for a specific hardware e.g in the: NETDEVTAB_ENTRY(DRV_netdev, "DRV", DRV_HRDWR_init, &DRV_sc); this has to become: NETDEVTAB_ENTRY(DM9000_netdev, "DRV", DM9000_init, &DM9000_sc); ETH_DRV_SC( DRV_sc, 0, // No driver specific data needed "eth0", // Name for this interface DM9000_start, DM9000_stop, DM9000_control, DM9000_can_send DM9000_send, DM9000_recv); So, where should this macro be invoked. Thanks --- Gary Thomas wrote: > On Tue, 2005-08-16 at 11:05 -0700, baljeet > singh wrote: > > All, > > I am trying to get DM9000 ethernet drivers > from > > MSalter with extensions by Stefan Rosinger to > > work on my hardware. I am not able to find > the > > call to MACRO > > NETDEVTAB_ENTRY(DRV_netdev, > > "DRV", > > DRV_HRDWR_init, > > &DRV_sc); > > That would create an entry in the dev table > for > > this device and also a call to MACRO > > ETH_DRV_SC(DRV_sc, > > 0, // No driver > specific > > data needed > > "eth0", // Name for this > > interface > > HRDWR_start, > > HRDWR_stop, > > HRDWR_control, > > HRDWR_can_send > > HRDWR_send, > > HRDWR_recv); > > > > that will setup the function calls. > > I am looking at dm900_drv.c and dm9000_info.h > > > > Is there anyother file that I should be > looking > > at? > > Or is this process of translation to specific > > device gets done in some fashion that I don't > > need to worry about. > > These macros are found in > > > -- > ------------------------------------------------------------ > Gary Thomas | Consulting for > the > MLB Associates | Embedded world > ------------------------------------------------------------ > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss