[ECOS] ftruncate for jffs2

[ECOS] ftruncate for jffs2

[Chakravarthy Ponnuri]

Hi,
 
I am using ecos2.0. Is there a implementation for ftruncate available for jffs2?
 
Thanks
Chakri


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

[ECOS] Ethernet controllers..

[Jim Bradleigh]

Hi,

I`ve a question regarding Ethernet controllers.

My platform is a i386 with 3 ethernet PCI controllers (but before you turn off, its more eCos related than platform). eCos only knows about the first controller, the other 2 use 'custom' drivers (copies of the original eCos ethernet driver but with a different interface for raw read/writes)

Is there any problem with using a different controllers? Say the main controller (eCos owned and operated) being a realtek card, whilst the other 2 being Intel based?

My concern is that there might be some PCI problems as I`ve read that u can`t mix drivers due to some PCI issues (but I think this might not affect me as eCos think's there's only one ethernet controller, the realtek card)

Regards,

Jim

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

Re: [ECOS] Ethernet controllers..

[David Brennan]

I think you will run into this
(http://sourceware.org/ml/ecos-discuss/2004-11/msg00191.html) if you
attempt to instantiate two different Ethernet drivers based on the
eCos code. I never did need to actually do anything with this, so I
don't have any code to share. Of course since you plan on modifying
one of the drivers, you can modify the relevant parts of that as well.

Good luck.
David


On Wed, Jan 13, 2010 at 2:12 AM, Jim Bradleigh
<jim.bradleigh1@btinternet.com> wrote:
> Hi,
>
> I`ve a question regarding Ethernet controllers.
>
> My platform is a i386 with 3 ethernet PCI controllers (but before you turn off, its more eCos related than platform). eCos only knows about the first controller, the other 2 use 'custom' drivers (copies of the original eCos ethernet driver but with a different interface for raw read/writes)
>
> Is there any problem with using a different controllers? Say the main controller (eCos owned and operated) being a realtek card, whilst the other 2 being Intel based?
>
> My concern is that there might be some PCI problems as I`ve read that u can`t mix drivers due to some PCI issues (but I think this might not affect me as eCos think's there's only one ethernet controller, the realtek card)
>
> Regards,
>
> Jim
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>

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

[ECOS] eCos problem: if_lancepci.c does not compile for i386 (vmWare)

[Waskita Adijarto]

I've just found problem compiling if_lancepci.c under eCos. After 
googling , I found similar problem in the archive here:  
http://www.mail-archive.com/ecos-discuss@ecos.sourceware.org/msg09854.html. 
I used similar new gnutools 
(ecoscentric-gnutools-i386-elf-20081107-sw.cygwin.tar.bz2)
I experienced this problem while compiling eCos 3.0 and 1.0.8 (from 
gaisler) in cygwin

Tool chain version:

    $ i386-elf-gcc -v
    Using built-in specs.
    Target: i386-elf
    Configured with: /gnutools/src/toolchains/gcc/gcc-4.3.2/configure -v --target=i386-elf --prefix=/gnutools/builds/toolchains/i386-elf/tools --with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --disable-__cxa_atexit --enable-threads --with-bugurl=http://bugs.ecos.sourceware.org/ --with-pkgversion='eCosCentric GNU tools 4.3.2-sw'
    Thread model: single
    gcc version 4.3.2 (eCosCentric GNU tools 4.3.2-sw)
      

My solution: use old gnutools 
(ecoscentric-gnutools-i386-elf-1.4-2.cygwin.tar.bz2) . The problem goes 
away.

tool chain version:

    $ i386-elf-gcc -v

    Reading specs from /opt/gnutools/i386-elf/bin/../lib/gcc-lib/i386-elf/3.2.1/specs

    Configured with: /local/demonweb/tools/ecos-gnutools-v1.4/r2/i386-elf/cygwin/tar_bz2/source/gcc-3.2.1/configure --target=i386-elf --prefix=/local/demonweb/tools/ecos-gnutools-v1.4/r2/i386-elf/cygwin/tar_bz2/opt/ecos/gnutools/i386-elf --enable-languages=c,c++ --with-gnu-as --with-gnu-ld --with-newlib --with-gxx-include-dir=/local/demonweb/tools/ecos-gnutools-v1.4/r2/i386-elf/cygwin/tar_bz2/opt/ecos/gnutools/i386-elf/i386-elf/include
    Thread model: single

    gcc version 3.2.1
      

I wonder why gcc 4.3.2 behave so different than 3.2.1

-waskita-


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

[ECOS] Ethernet controllers..

[Jim Bradleigh]

Hi,

Thought I would throw this out to the list to see if anyone can help...

As everyone know's eCos supports a limited device driver list for each platform, I`m currently running on i386 which limits me to a real-tek and two Intel chipsets...

Where do most of you purchase network controllers from? I can`t find any network cards which say they contain the Intel i82544 chipset.. It would be nice to start my project with a defined hardware spec that I know I can purchase..

One other question, does anyone know if a network card with the Marvell 88E1111 chipset exists?

Thanks,

Jim


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