Pedro,
Thanks for your reply. And I agree with you that interfaces (from OS kernel)
is the point that a driver develop should take care of. Now it's clearer for me
to understand the capability of cegcc. Cegcc is already a great tool that
helps me to port Linux applications!
BTW, the reason that I'd not start from here is that I want to get a working
driver as fast as I could, based on the Linux ACX100 drivers.
Cheer!
- Ling
Bell Labs Research China
Http://qianwuge.spaces.live.com/
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pedro Alves
Sent: 2007年7月10日 下午(五哥)18:22
To: Qian, Ling (Ling)
Cc: Danny Backx; CeGCC Development List
Subject: Re: [Cegcc-devel] Can cegcc cross compile network driver
On 7/10/07, Qian, Ling (Ling) wrote:
>
> 1. ACX100 driver is linked against the Linux kernel, what is the
> module to be linked in cegcc? is it libcoredll.a? ( I am downloading
> the src of cegcc, it needs some time :)
>
> 2. What is the relationship between the WinCE NDIS and libcoredll.a, which
> one is sitting on higher layer? I have read and write sth related to NDIS
> protocol driver, I get to know that NDIS has 3 kinds of layers. The bottom is
> the miniport driver, which is the hardware driver. If ACX100 driver can be
> ported to WinCE, it should be one of the NDIS miniport driver, right?
>
> 3. The good thing on WinCE is that all drivers are DLL files, which can be
> loaded dynammically.
>
> 4. There are functions like (in ACX100 PCI driver): write_reg32(),
> write_flush(), are these functions supported in cegcc?
>
You're confused a bit on the basics. coredll.dll is a Windows CE system
component. It exports most libc routines, and most win32 api functionality.
Most everything you'll write links with coredll.dll. libcoredll.a is our
import lib to coredll.dll.
First, you shouldn't write a driver with cegcc. At most with mingw32ce. The
dependency cegcc imposes on cegcc.dll is IMHO unacceptable for a driver.
But you're really ringing at the wrong bell. There are good forums for
discussion on driver development for CE (eg:
microsoft.public.windowsce.embedded). Perhaps you should start there *after*
you've studied the extensive documentation over at MSDN, have a look at
examples, etc, etc.
On the mingw32ce side, you may find that we miss a few headers and definitions,
and perhaps even missed to export a function from some import lib - that's the
part we can fix. Porting a driver between OSs has mostly nothing to do with
the compiler, but with using the correct interfaces.
Cheers,
Pedro Alves
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel
