SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 29 | December | 2001 ]

>> Next Message >>


Date: Sat, 29 Dec 2001 01:09:46 PST7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Device driver: was Linksys Wireless Access Point

=====================================================
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.

Peter trivializes the work required to write a driver. It really depends
on the device. Adapting an existing driver to dump bits out to a DAC is
pretty simple. Adapting an existing sound card driver to drive a
different chipset is significantly more work. Writing a firewire driver
is even more work.

>Getting device manufactures to make detailed functional information
>available will be the big hurdle. If we can get the info. we can solve

This is not the problem it used to be. Most of the cards out there use
commodity chips and reference designs.

>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.

>Is this doable or am I an academic living in an ivory tower?

It's very doable for anyone willing to invest the time. Of course, the
first one is always the most difficult. This is where you get to figure
out which header file contains what and so on.

Steven

--
----------------------------------------------------------------
"Steven Levine" MR2/ICE 2.30a #10183 Warp4/FP15
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
----------------------------------------------------------------

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

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".

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


>> Next Message >>

Return to [ 29 | December | 2001 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.