Hello,
Is there any person(s) developing a driver for DAT-chipset-based
Creative sound cards?
If this is the wrong mailing list to ask this question, please tell me
which is the proper list.
Regards,
John McCabe
___
freebsd-questions@freebsd.org
this? Is it
possible to do everything in userspace? Under Linux, there appears to
be something called FUSD, which allows one to write userspace device
drivers. Is there anything similar under FreeBSD?
Ideally I'd like to keep the resulting solution as generic as possible,
so that it can
anyone point me in right direction towards achieving this? Is it
possible to do everything in userspace? Under Linux, there appears to
be something called FUSD, which allows one to write userspace device
drivers. Is there anything similar under FreeBSD?
Do you mean FUSE? There is FUSE
/lircX.
Can anyone point me in right direction towards achieving this? Is it
possible to do everything in userspace? Under Linux, there appears to
be something called FUSD, which allows one to write userspace device
drivers. Is there anything similar under FreeBSD?
Do you mean FUSE
out which would be best, to load all the device
drivers through compiling them into the kernel or to load them at boot
through loader.conf.
I would think that loader.conf would be more convenient as changing
hardware
wuld not require a rebuild of the kernel. Is there a draw back to
loading
David Wassman [EMAIL PROTECTED] writes:
I am trying to figure out which would be best, to load all the device
drivers through compiling them into the kernel or to load them at boot
through loader.conf.
I would think that loader.conf would be more convenient as changing hardware
wuld
--- Lowell Gilbert
[EMAIL PROTECTED] wrote:
David Wassman [EMAIL PROTECTED] writes:
I am trying to figure out which would be best, to
load all the device
drivers through compiling them into the kernel or
to load them at boot
through loader.conf.
I would think that loader.conf
I am trying to figure out which would be best, to load all the device
drivers through compiling them into the kernel or to load them at boot
through loader.conf.
I would think that loader.conf would be more convenient as changing hardware
wuld not require a rebuild of the kernel. Is there a draw
to FreeBSD.
I want to start writing device drivers, and would love any pointers to
resources and tips from anyone. At the moment I'm reading a good C
primer, along with The Design and Implementation of The FreeBSD
Operating System ( a great book), and browsing the relevant sections
in the Handbook
Hi everyone, hope this isn't too off topic. I'm a sysadmin who taught
myself programming (and have worked as a PHP ad MYSQL developer) and
really want to develop my FreeBSD skills, and hopefully one day be
able to give something back to FreeBSD.
I want to start writing device drivers, and would
Hi,
I've been searched Google for few days but still can't
find any info about how to develop device drivers for
Intel IXP in FreeBSD.
Can anyone please tell me some guideline and reference
for it?
I will be very appreciate for any suggestion.
Thanks
Sam
Hello,
Is there a way to manually assign device drivers to PCI cards on an
x86 system with FreeBSD 4.11? I want to assign fxp0 to the nic card in the
first PCI slot, fxp1 to the second PCI slot, fxp2 to the third, etc.
Is there any way to accomplish this?
Thanks
there will be no slow-down, and most other cases
probably won't need very much code and might be just inline functions.
I'd like to do this in a way that many device drivers can use this api
to help make them more portable between kernels. Now some parts may
require very drastic code differences and need
Gregory Nutt wrote:
I'm trying to port the device driver for acx100 chipsets TO WORK ON
FreeBSD. However, all the guides I'm finding make reference to files
that apparently are no longer used such as:
card_if.h
device_if.h
bus_if.h
etc...
and have been renamed to card_if.m, device_if.m,
I'm trying to port the device driver for acx100 chipsets TO WORK ON
FreeBSD. However, all the guides I'm finding make reference to files that
apparently are no longer used such as:
card_if.h
device_if.h
bus_if.h
etc...
and have been renamed to card_if.m, device_if.m, bus_if.m, etc...
even
I hope this is the right list, I have a nforce 2 board and have
drivers that aren't working. I read the nforce was based ond the amd
chipset so I tried to use /sys/pci/agp_amd.c as a blueprint and modified
it according to the data in /src/pci/agp_nvidia.c. I am maybe half done
and learned
unix wrote:
Hi,
I am looking for some good documentation to get a head start in FreeBSD device driver programming. Can any of you gurus provide me with some pointers regarding the availability of such documentation?
Thanx in advance...
___
Hi,
I am looking for some good documentation to get a head start in FreeBSD device driver
programming. Can any of you gurus provide me with some pointers regarding the
availability of such documentation?
Thanx in advance...
___
From what I can tell, the compatibility in FreeBSD for Linux binaries
does _not_ apply to commercial binary-only Linux device drivers, it
only applies to applications. Is that correct?
Thanks,
Jeff Walters
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions
Jeff Walters writes:
From what I can tell, the compatibility in FreeBSD for Linux binaries
does _not_ apply to commercial binary-only Linux device drivers, it
only applies to applications. Is that correct?
Correct.
---
Gary Jennejohn / [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL
20 matches
Mail list logo
