* [ECOS] Re: modification for CYGPKG_DEVS_ETH_POWERPC_FCC package
[not found] <20031215142522.98966.qmail@web25003.mail.ukl.yahoo.com>
@ 2003-12-15 15:51 ` Gary Thomas
0 siblings, 0 replies; only message in thread
From: Gary Thomas @ 2003-12-15 15:51 UTC (permalink / raw)
To: alix t; +Cc: eCos Discussion
Note: this question belongs on ecos-discuss. The maintainer's
list is only for questions dealing with the management of the
project, not porting details, etc.
On Mon, 2003-12-15 at 07:25, alix t wrote:
> Hi,
>
> I currently develop application for a motorola
> evaluation card ( PQ2FADS-VR with MPC8275).
> I use CYGPKG_DEVS_ETH_POWERPC_FCC package for the
> ethernet driver.
> But PQ2FADS-VR board use FCC2 anf FCC3 and
> CYGPKG_DEVS_ETH_POWERPC_FCC package in only coded for
> FCC1 and FCC2.
> Is it possible to add some code to manage FCC3?
>
>
> Modifications are the following:
>
> In file if_fcc.c:
>
> in function fcc_eth_init(struct cyg_netdevtab_entry
> *dtp)
>
> + case CYGNUM_HAL_INTERRUPT_FCC3:
> + qi->fcc_reg = &(IMM->fcc_regs[FCC3]);
> + fcc = (volatile t_Fcc_Pram *)((unsigned long)IMM +
> FCC3_PRAM_OFFSET);
> + fcc_chan = FCC3_PAGE_SUBBLOCK;
> + break;
>
> In file fcc.h:
>
> + #define FCC3 2
> + #define FCC3_PRAM_OFFSET 0x8600 // Offset of
> t_Fcc_Pram in 82xx
Look at how this is handled for the A&M Rattler - adding a
third (or different) device should not be difficult.
.../devs/eth/powerpc/ratter
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-12-15 14:30 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20031215142522.98966.qmail@web25003.mail.ukl.yahoo.com>
2003-12-15 15:51 ` [ECOS] Re: modification for CYGPKG_DEVS_ETH_POWERPC_FCC package Gary Thomas
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).