This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: NIC support for x86 PC using dp83815 ethernet controller needed


"Kevin S. Martin" <ksmartin@fnal.gov> writes:

> Hey,
> 
> I'm trying to get redboot (and eCos) to run on a x86 PC (Diamond
> System's Hercules EBX). It uses a dp83815 ethernet controller. I see
> that there is some support for the dp83816. But this seems to be for
> use in a different architecture (PPC?).
> 
> What needs to be changes for it to work under i386?
> 
> I can build a redboot.bin using the i386 template redboot package. I
> can boot the system(using a floppy disk) with this binary but of
> course it doesn't find a NIC because the default NIC is a i82559. I
> then remove the default ethernet controller (i82559) packages and add
> the dp83816 package:
> 
> [root@bdeelinux packages]# ecosconfig --config=redboot.ecc check
> Target: pc
> Template: redboot
> Added:
>  CYGPKG_IO_ETH_DRIVERS
>  CYGPKG_DEVS_ETH_NS_DP83816
> Removed:
>  CYGPKG_DEVS_ETH_INTEL_I82559
>  CYGPKG_DEVS_ETH_I386_PC_I82559
> No conflicts
> 
> After doing this, redboot still doesn't find a NIC. Has anyone else
> used a dp83816 or dp83815 on PC?
> 

You need to create a new package to customize the generic DP83816
driver to the hardware. Take the MOAB package, copy it, rename it, and
adapt it to the PC. Since it is a PCI device, you probably dont need
to do very much. Now add that package to the configuration.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com      The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]