SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Tue, 1 Jan 2002 21:42:38 PST7
From:	Sheridan George <s-geo@usa.net >
Reply-To:	scoug-help@scoug.com
To:	Scoug Help Desk <scoug-help@scoug.com >
Subject:	SCOUG-Help: Device driver: was Linksys Wireless Access Point]

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

For some reason this was returned "mail refused by host" and seemed to refer to
khill2@mindspring.com

So, I'm trying it again.

Sheridan

-------- Original Message --------
Subject: Re: SCOUG-Help: Device driver: was Linksys Wireless Access Point
Date: Mon, 31 Dec 2001 15:23:46 -0800
From: Sheridan George
To: scoug-help@scoug.com
References:

Steven Levine wrote:
>
> =====================================================
> If you are responding to someone asking for help who
> may not be a member of this list, be sure to use the
> REPLY TO ALL feature of your email program.
> =====================================================
>
> In <3C2D3114.CE25013A@usa.net>, on 12/28/01
> at 06:57 PM, Sheridan George said:
>
> >Maybe we should entertain a change from the programming SIG (which seems
> >to have fallen by the wayside) to a device driver SIG.
>
> I'm just waiting for some workers to show up.
>
> >Learning how to create device drivers is probably not that big a problem.
>
> It is and it isn't. All the tools and samples are free for the asking
> from IBM's DDK site. Working sample code is available. Watcom 11.0c is
> now available from OpenWatcom. That said, you need to understand the
> driver architecture and understand how to use the tools and understand how
> to effectively test a driver.

If the Watcom 11.0c compiler is for C of C++ then there is another problem. I'm among the few
(several?) that does not write (and understands only a little) C or C++. That may be the biggest
hurdle. Besides C, C++, and Assembler what other languages does it make sense to use for devise
drivers?

> >at least some driver problems for our selves. Or maybe we can learn how
> >to port Linux drivers.
>
> Much of the work has already been done for you. See the drivers available
> at Netlabs.

I can read what you wrote but since I don't know the relationship between Linux and OS/2 drivers I
don't understand what you mean by "see the drivers ... Netlabs".

Sheridan

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 01 | January | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.