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 [ 28 | December | 2001 ]

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


Date: Fri, 28 Dec 2001 19:47:00 PST7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: 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.
=====================================================

Sheridan George wrote:
>
> Maybe we should entertain a change from
> the programming SIG to a device driver SIG.
>
> Learning how to create device drivers
> is probably not that big a problem.
>
> Is this doable or am I an academic living in an ivory tower?

Device drivers aren't complicated, but when I was playing with writing
them a few years ago it seemed that people were arguing about the
semantics of "device driver" rather than working on writing them.

It helps to have two machines hooked together through the COM ports.
You write the driver on one machine and execute it on the other. Then
when it blows up and you have to reboot, you can keep working on the
development machine rather than waiting for the boot to complete. And
the COM connection can tie into a "debug" version of the kernel so you
can trace what's going on if you want to.

Drivers are just little programs. There's no magic involved.

> Getting device manufactures to make detailed functional
> information available will be the big hurdle.
>
> If we can get the info. we can solve at least
> some driver problems for ourselves. Or maybe
> we can learn how to port Linux drivers.

My favorite tool is a disassembler. I would disassemble the DOS driver
and see what the necessary actions were.

Linux drivers should be just as easy. I'm sure there are Linux
disassemblers. (From what I've read, a lot of the Linux drivers are
_not_ "open source".)

You can't readily "port" a Linux driver because the driver model is
different, but you can swipe all the important code algorithms.

Somewhere around here I have my books on writing device drivers for OS/2
and for Linux.

- Peter

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

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

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


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

Return to [ 28 | 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.