From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12220 invoked by alias); 22 Oct 2008 15:45:52 -0000 Received: (qmail 12201 invoked by uid 22791); 22 Oct 2008 15:45:51 -0000 X-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from smtp-04.vtx.ch (HELO smtp-04.vtx.ch) (212.147.0.65) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 22 Oct 2008 15:44:57 +0000 Received: from [127.0.0.1] (dyn.83-228-181-132.dsl.vtx.ch [83.228.181.132]) by smtp-04.vtx.ch (VTX Services SA) with ESMTP id F169429AE09; Wed, 22 Oct 2008 17:10:28 +0200 (CEST) Message-ID: <48FF4AA5.8050007@snr.ch> Date: Wed, 22 Oct 2008 15:45:00 -0000 From: "Oliver Munz @ SNR" Reply-To: oli@snr.ch Organization: SNR User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Gary Thomas CC: "ecos-devel@sourceware.org" Subject: Re: If i need a supportet microcontroller with a new ethernet PHY... References: <48FF3FE1.6080309@snr.ch> <48FF41D0.8050007@mlbassoc.com> In-Reply-To: <48FF41D0.8050007@mlbassoc.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 081022-0, 22.10.2008), Outbound message X-Antivirus-Status: Clean Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2008-10/txt/msg00003.txt.bz2 Atmel AT91SAM7X connected to a Micrel KSZ8041... Now i write a plattform variant named CYGPKG_HAL_ARM_AT91SAM7X_KSZ8041, but i'm not sure if this is the ecos-way to do it... Gary Thomas schrieb: > Oliver Munz @ SNR wrote: > >> ... then i have to rewrite the void hal_plf_eth_init(void). I can make a >> new platform-variant for this, but may be there is a better solution >> like: make the hal_plf_eth_init PHY-dependent or make it configurable >> defined as external or something like this... >> >> The problem is, that every PHY has other initalisation requirements. And >> furthermore its a question of the concrete hardware what the CPU has to >> do to bring it to work. So the hal_plf_eth_init depens on the PHY, the >> ethernet and microcontroller and the concret circuit... >> >> What is the best way to use a special hal_plf_eth_init()? >> > > What's the platform/target? > >