*BSD This forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
02-10-2005, 07:02 PM
|
#1
|
|
Member
Registered: Feb 2003
Location: York, PA
Distribution: Slackware, FreeBSD, OpenBSD
Posts: 162
Rep:
|
Naming device driver
I'm going to be creating a device driver for the OpenBSD kernel (particularly a network card driver), any idea how naming the device works? I'm not really sure how the names are conventionally came about to, for example here is a network card "fxp0", or, "xl0". Thanks ahead of time.
|
|
|
|
02-11-2005, 08:06 AM
|
#2
|
|
Senior Member
Registered: Jan 2004
Location: Roughly 29.467N / 81.206W
Distribution: Ubuntu, FreeBSD, NetBSD
Posts: 1,449
Rep:
|
Traditionally, the device is named with some abbreviation of the chipset it is designed to control.
Code:
The xl driver provides support for PCI ethernet adapters and embedded
controllers based on the 3Com "boomerang," "cyclone," "hurricane" and
"tornado" bus-master Etherlink XL chips
This may not always be the case but if your chipset has some easy, unused abbreviation, then it might be best to go in that direction. But the best idea would be designing it then asking what name would be best for it (have a good working name in case so they can choose to leave the name as you designed it if that is their choice) and be willing to change the name if they come up with one that is more intune with their ideas.
|
|
|
|
02-12-2005, 10:46 AM
|
#3
|
|
Member
Registered: Feb 2003
Location: York, PA
Distribution: Slackware, FreeBSD, OpenBSD
Posts: 162
Original Poster
Rep:
|
Alright, thanks. I was thinking about doing that, but I was caught up on naming the functions correctly and didn't feel like going back and changing everything, then I remembered sed 
Thanks again.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 01:40 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|