It doesn't seem to work. I've got 22 2.0TB SATA disks, and a 120GB
Intel SSD attached, I get these messages, and the drives all show in
dmesg and /dev.
But if I try writing to any of them, the process just hangs.
Anyone reported success with the 2760A?
hpt27xx: RocketRAID 27xx controller driver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 04/20/12 17:16, Barkley Vowk wrote:
> It doesn't seem to work. I've got 22 2.0TB SATA disks, and a 120GB
> Intel SSD attached, I get these messages, and the drives all show
> in dmesg and /dev.
>
> But if I try writing to any of them, the p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/12/12 10:14, Barkley Vowk wrote:
> I've got a Highpoint 2760A card that I'd like a FreeBSD driver
> for, I've got a machine and disks available if someone wants to
> tackle that.
Please try loading 'hpt27xx.ko' on boot.
Cheers,
- --
Xin LI
I've got a Highpoint 2760A card that I'd like a FreeBSD driver for,
I've got a machine and disks available if someone wants to tackle
that.
Thanks!
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To
me NIC
installed that have not had any problems.
So, my question,
Is it easily possible to use the igb drivers from 8.2-RELEASE on 8.1-RELEASE
and load them as a module? If so what would be the best way to accomplish this
? This is more just a kind of exploration for myself rather than
On 9/6/11 8:03 PM, Adrian Chadd wrote:
On 7 September 2011 09:32, Adam Vande More wrote:
On Tue, Sep 6, 2011 at 7:50 PM, Stephen Hocking
wrote:
Am wondering if anyone has done drivers the these sorts of network
interfaces that are offered by VMWare& Virtual box. I know that on
some L
On 7 September 2011 09:32, Adam Vande More wrote:
> On Tue, Sep 6, 2011 at 7:50 PM, Stephen Hocking
> wrote:
>
>> Am wondering if anyone has done drivers the these sorts of network
>> interfaces that are offered by VMWare & Virtual box. I know that on
>> some Li
On Tue, Sep 6, 2011 at 7:50 PM, Stephen Hocking
wrote:
> Am wondering if anyone has done drivers the these sorts of network
> interfaces that are offered by VMWare & Virtual box. I know that on
> some Linux VMs I run, performance went from 20MB/s to 30MB/s to an NFS
> server whi
Hi all,
Am wondering if anyone has done drivers the these sorts of network
interfaces that are offered by VMWare & Virtual box. I know that on
some Linux VMs I run, performance went from 20MB/s to 30MB/s to an NFS
server which I swicthed to the virtio network interfaces.
Ste
If I could, let me ask another question. My device could potential have up
to 6 BARs, that would be mapped into user space. Should I simply bundle
them together in my driver into one contiguous space or should I make the
user perform multiple mmap calls? If I go the multiple mmap route, how do I
On 06/07/2010, at 5:32, Christopher Bowman wrote:
> If I could, let me ask another question. My device could potential have up
> to 6 BARs, that would be mapped into user space. Should I simply bundle them
> together in my driver into one contiguous space or should I make the user
> perform m
On 26/06/2010, at 14:50, Christopher Bowman wrote:
>> PS what board are you using? :)
>>
> Cool, that looks like what I am looking for. I'll go and read up on it,
> thanks very much. I am using the Xilinx SP605
> http://www.xilinx.com/products/devkits/EK-S6-SP605-G.htm
> perfect for playi
On Fri, Jun 25, 2010 at 8:18 PM, Daniel O'Connor wrote:
>
> On 26/06/2010, at 3:01, Christopher Bowman wrote:
> > I have a Xilinx PCI Express board that has an on board PCIe interface
> > macro. I intend to have an address space with memory and another with my
> > devices control registers. I wi
On 26/06/2010, at 3:01, Christopher Bowman wrote:
> I have a Xilinx PCI Express board that has an on board PCIe interface
> macro. I intend to have an address space with memory and another with my
> devices control registers. I wish to program this board under FreeBSD. It
> would seem to me tha
I have a Xilinx PCI Express board that has an on board PCIe interface
macro. I intend to have an address space with memory and another with my
devices control registers. I wish to program this board under FreeBSD. It
would seem to me that the way to do this would be to write a driver that
would
esent in Freebsd 6.1? How easy would it
> to backport this to 6.1?
> If yes, then is there a way to disable the skgeinit(which seems to be the
> default) and enable the sky2 driver?
>
> Anjali
In linux, sure, there are two drivers for Marvel Yukon cards, called
skgeinit and sky2. Thi
Hi,
As I understand, there are 2 flavors of the Marvel Yukon driver. One is for
Yukon-I devices, and is called skgeinit, and other is for Yukon-II devices and
called sky2 driver.
Looking at the release notes for 7.0, it looks like this driver which was in
sys/dev/yukon, is now present as the m
On Tuesday 11 August 2009 08:06:26 Krassimir Slavchev wrote:
> Hans Petter Selasky wrote:
> > On Monday 10 August 2009 13:39:31 Krassimir Slavchev wrote:
> >> If I try to open the device from userland with:
> >> fd = open("/dev/xxx0", O_RDWR) it fails because open() tries to open the
> >> device fo
Hans Petter Selasky wrote:
> On Monday 10 August 2009 13:39:31 Krassimir Slavchev wrote:
>> If I try to open the device from userland with:
>> fd = open("/dev/xxx0", O_RDWR) it fails because open() tries to open the
>> device for reading first and then for writing.
>
> There is a bug in the code.
freebsd-hackers-requ...@freebsd.org
You can reach the person managing the list at
freebsd-hackers-ow...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-hackers digest..."
Today's Topics:
1. Help with device dr
On Monday 10 August 2009 13:39:31 Krassimir Slavchev wrote:
> If I try to open the device from userland with:
> fd = open("/dev/xxx0", O_RDWR) it fails because open() tries to open the
> device for reading first and then for writing.
There is a bug in the code. If you open using read+write flags,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
Looking at sys/dev/usb/misc/ufm.c
...
static int
ufm_open(struct usb_fifo *dev, int fflags)
{
if ((fflags & (FWRITE | FREAD)) != (FWRITE | FREAD)) {
return (EACCES);
}
return (0);
}
...
and sys/dev/usb
> Alexander Motin wrote:
> > Danny Braniss wrote:
> >> wups, forgot a small little detail:
> >> ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.2.3.tar.gz
> >
> > Is there reason why
> > cpi->transport = XPORT_ISCSI;
> > covered by
> > #if defined(KNOB_VALID_ADDRESS)
> > ?
>
I needed
Hi.
Danny Braniss wrote:
wups, forgot a small little detail:
ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.2.3.tar.gz
Is there reason why
cpi->transport = XPORT_ISCSI;
covered by
#if defined(KNOB_VALID_ADDRESS)
?
--
Alexander Motin
___
Alexander Motin wrote:
Danny Braniss wrote:
wups, forgot a small little detail:
ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.2.3.tar.gz
Is there reason why
cpi->transport = XPORT_ISCSI;
covered by
#if defined(KNOB_VALID_ADDRESS)
?
Sorry, wrong question. But those who will test
wups, forgot a small little detail:
ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.2.3.tar.gz
danny
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "fr
This new version:
o - has some bug fixes.
o - has full header/data digest support, thanks to Daisuke Aoyama
.
o - the limit for the number of sessions is now 64, but can be
raised - eventually via a sysctl call.
o - the number of LUNs is unlimited, but things might get hairy
over
This approach, for creating drivers from Linux source, will probably be
moved into userland in one way or another, but for now I'm going to see if
I can make some progress by getting some Linux webcam drivers working.
The problem I'm currently wrestling with is how to manage the emulat
Hi Folks:
I'm debugging an issue with a third-party driver that causes an NMI
during driver initialization. It only occurs for one version of the
driver thus far. I want to isolate what triggers the NMI and
generally get a feel for the initialization of the hardware.
I'm running a 6.x-amd64 ker
On Thu, 25-Dec-2008 at 13:57:00 +, Rui Paulo wrote:
>
> On 25 Dec 2008, at 09:53, Andre Albsmeier wrote:
>
> > Hello all,
> >
> > I am writing a driver which needs to access memory at a
> > specific location. The location depends on what the BIOS
> > has configured into the host bridge. For e
On 25 Dec 2008, at 09:53, Andre Albsmeier wrote:
Hello all,
I am writing a driver which needs to access memory at a
specific location. The location depends on what the BIOS
has configured into the host bridge. For example, my
current machine uses an Intel 975X chipset and the memory
location I
Hello all,
I am writing a driver which needs to access memory at a
specific location. The location depends on what the BIOS
has configured into the host bridge. For example, my
current machine uses an Intel 975X chipset and the memory
location I am interested in has been set to 0xFED14000 and
is 1
On October 17, 2008 01:21 pm Oleg wrote:
> Hello maillist of my favorite Wortstation&Server OS
>
> May i asking: how i can determine all drivers of existing devices, but
> who is not present in GENERIC kernel.
> My question: what the "official" FreeBSD-way for the
Hello maillist of my favorite Wortstation&Server OS
May i asking: how i can determine all drivers of existing devices, but who is
not present in GENERIC kernel.
For definition of all devices useful to me I have written the following a
little stupid script:
--
#!/bin/sh
MODLIST=`
s controller directly. The driver I'm writing is
: not a PCI or PCI device driver either.
:
: Hope someone can help me out on this one, it's important that there's
: no user-space code...
Generally, you don't want to scan the PCI bus to look for drivers to
talk to. That's
Hello,
I need to access the hard disk from within a driver that is not a FS.
I would also need to get a list of PCI devices connected. Is there a
way I can access these devices directly, at least in the first case,
issuing directly ATA/IDE commands to the hard disk?
In the case of PCI it would be
er versions - the
backport to 4.x would probably require significant effort.
>KVM has now special drivers, based on the virtio specifications. These
>drivers are compiled for windows and linux but unfortunately not for
>BSD. I think that they are pretty simple in the guest side (75kb of
&
Hi all,
I'm currently using linux KVM as an hypervisor and I would like to use
an old freebsd4 machine as a guest. The thing is that machine is very
network consuming, so it would be great to have special drivers.
KVM has now special drivers, based on the virtio specifications. These
driver
Hello guys!
I am interested in your opinion regarding this topic:
http://nico.schottelius.org/notizbuch-blog/archive/2008/04/24/where-to-put-mouse-drivers
Thanks for any feedback,
Nico
--
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the
[EMAIL PROTECTED] wrote:
Hi, all,
the scripts in /usr/share/examples/drivers,
Author: Julian Elischer
create two isa skeletons for drivers.
i would like to create a skeleton for a pci driver.
Please, can you help me by pointing out all diffs needed for this purpose?
Thanks for your
Hi, all,
the scripts in /usr/share/examples/drivers,
Author: Julian Elischer
create two isa skeletons for drivers.
i would like to create a skeleton for a pci driver.
Please, can you help me by pointing out all diffs needed for this purpose?
Thanks for your suggestions.
[EMAIL PROTECTED
In message: <[EMAIL PROTECTED]>
"Andrew Duane" <[EMAIL PROTECTED]> writes:
: I may have asked this once before, but are any NOR flash drivers
: available in FreeBSD? I have support that I put into the bootstrap I'm
: building, interfaced to libstand, but it
I may have asked this once before, but are any NOR flash drivers
available in FreeBSD? I have support that I put into the bootstrap I'm
building, interfaced to libstand, but it is read-only, and far from
useful for a real UFS.
--
Andrew Duane Juniper Networks
978-589
Garrett Cooper <[EMAIL PROTECTED]> writes:
> Julian Elischer <[EMAIL PROTECTED]> writes:
> > I Believe the linux wrapper concept was copied from the freebsd one
> > which was originally called "Project Evil"
> Is it the other way around (Project Evil isa ndiswrapper port, etc),
> or something else.
В сообщении от Friday 25 January 2008 11:25:33 Garrett Cooper написал(а):
> On Jan 24, 2008, at 5:29 PM, Julian Elischer wrote:
> > Yuri wrote:
> >> I am curious is there an effort in FreeBSD similar to Linux
> >> NDISwrapper?
> >> NDISwrapper taked Windows XP binary driver and runs it on Linux.
>
On Jan 24, 2008, at 5:29 PM, Julian Elischer wrote:
Yuri wrote:
I am curious is there an effort in FreeBSD similar to Linux
NDISwrapper?
NDISwrapper taked Windows XP binary driver and runs it on Linux.
http://ndiswrapper.sourceforge.net/joomla/
They add the converter between Linux kernel API
binary driver.
I Believe the linux wrapper concept was copied from the freebsd one
which was originally called "Project Evil"
I know that few USB Webcams are supported in the similar way on FreeBSD
recompiling Linux source drivers. Also Mplayer is using similar
approach wrapping arou
On Thu, Jan 24, 2008 at 04:12:00PM -0800, Yuri wrote:
> I am curious is there an effort in FreeBSD similar to Linux NDISwrapper?
man 4 ndis
Joerg
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To u
On Thu, Jan 24, 2008 at 04:12:00PM -0800, Yuri wrote:
> I am curious is there an effort in FreeBSD similar to Linux NDISwrapper?
http://www.freebsd.org/cgi/man.cgi?query=ndis&apropos=0&sektion=0&manpath=FreeBSD+6.3-RELEASE&format=html
-- Rick C. Petty
_
kernel API and the subset of
> Windows kernel API sufficient to run binary driver.
>
> I know that few USB Webcams are supported in the similar way on FreeBSD
> recompiling Linux source drivers. Also Mplayer is using similar
> approach wrapping around Windows-only binary codecs.
&g
.
I know that few USB Webcams are supported in the similar way on FreeBSD
recompiling Linux source drivers. Also Mplayer is using similar
approach wrapping around Windows-only binary codecs.
But is these such thing for network cards on FreeBSD?
Yuri
I suggest looking at John-Mark Gurney's 2006 BSDCan presentation:
http://www.bsdcan.org/2006/papers/freebsd.device.driver.slides.pdf
http://www.bsdcan.org/2006/papers/freebsd.driver.pdf
--
/"\ Best regards, | [EMAIL PROTECTED]
\ / Max Laier | ICQ
Thanks,
Thierry
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Sun, Jul 01, 2007 at 01:26:09AM -0700, Josef Grosch wrote:
> 3) 3ware's new SATA RAID controller (9500)
Latest -stable seems to have this already; at least one that's recent
enough for a shiny new 9650SE to work (which doesn't work in 6.2
release).
Craig
___
On Sun, 1 Jul 2007 11:58:27 +0200
Erik Trulsson <[EMAIL PROTECTED]> wrote:
> The msk(4) driver should support that chip. This driver is also
> available in both -CURRENT and 6-STABLE and thus will appear in both
> FreeBSD 6.3 and 7.0.
great! is it as good as Marvell's one?
[SorAlx] ridin' VN150
On Sun, Jul 01, 2007 at 02:30:00AM -0700, [EMAIL PROTECTED] wrote:
> On Sun, 1 Jul 2007 01:26:09 -0700
> Josef Grosch <[EMAIL PROTECTED]> wrote:
>
> > There are 3 drivers that I have been using with FreeBSD 6.2-RELEASE
> > and 6.2-RELEASE-p5. They are
> >
On Sun, Jul 01, 2007 at 02:30:00AM -0700, [EMAIL PROTECTED] wrote:
> On Sun, 1 Jul 2007 01:26:09 -0700
> Josef Grosch <[EMAIL PROTECTED]> wrote:
>
> > There are 3 drivers that I have been using with FreeBSD 6.2-RELEASE
> > and 6.2-RELEASE-p5. They are
> >
>
On Sun, 1 Jul 2007 01:26:09 -0700
Josef Grosch <[EMAIL PROTECTED]> wrote:
> There are 3 drivers that I have been using with FreeBSD 6.2-RELEASE
> and 6.2-RELEASE-p5. They are
>
> 1) Intel's new driver for em
>
> 2) Adaptec's new driver for the 3805
>
There are 3 drivers that I have been using with FreeBSD 6.2-RELEASE and
6.2-RELEASE-p5. They are
1) Intel's new driver for em
2) Adaptec's new driver for the 3805
3) 3ware's new SATA RAID controller (9500)
The drivers can be found :
Intel:
http://downloadc
On Mar 30 at 12:02 -0700, Maksim Yevmenkin wrote:
> On 3/29/07, Timothy Bourke <[EMAIL PROTECTED]> wrote:
> >It seems that, for the extant drivers:
> >* enable only increments kb_active,
> >* disable only decrements kb_active.
>
> well, yes, if all
it is released from
> kbdmux. it is perfectly fine, imo, to have two (or more) active
> keyboards attached to the system as long as only one of them is
> primary. it is possible to use /dev/kbdX interface to talk to
> non-primary keyboard(s) directly.
It seems that, for the extant dri
re) active
> keyboards attached to the system as long as only one of them is
> primary. it is possible to use /dev/kbdX interface to talk to
> non-primary keyboard(s) directly.
It seems that, for the extant drivers:
* enable only increments kb_active,
* disable only decrements kb_active
hooks, but these do not seem to be called
properly. Hence this post.
The enable and disable functions are identical across the keyboard
drivers (atkbd, ukbd, vkbd, kbdmux). Enable calls the KBD_ACTIVATE macro
which increments the kb_active count. Disable calls the KBD_DEACTIVATE
macro which decremen
post.
The enable and disable functions are identical across the keyboard
drivers (atkbd, ukbd, vkbd, kbdmux). Enable calls the KBD_ACTIVATE macro
which increments the kb_active count. Disable calls the KBD_DEACTIVATE
macro which decrements the kb_active count. It seems reasonable to
assume that the
Quoting "M. Warner Losh" <[EMAIL PROTECTED]> (from Tue, 11 Jul 2006
10:32:03 -0600 (MDT)):
As to your other points, the resource allocation repetition has been
improved with bus_alloc_resources. the trouble is that many drivers
haven't been converted to use the new ap
On Friday 09 June 2006 04:16, [EMAIL PROTECTED] wrote:
> My problem seems to be very special. My driver module is a single one, but
> I want to build only one object for each directory (such as osd.o: osd/*.c;
> engine.o: engine/*.c; cam.o:cam/*.c). And my driver module (such as
> Shasta.ko) is con
On Thursday 08 June 2006 12:13, [EMAIL PROTECTED] wrote:
> Hi guys:
>
>
>
> Need your helps again! The following is a Makefile template for a device
> driver in FreeBSD. But when my driver source codes locate in multiple
> directories (such as under osd/, engine/, and cam/), how to write the
> Make
On 08.06.2006, at 14:13, <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> wrote:
Need your helps again! The following is a Makefile template for a
device
driver in FreeBSD. But when my driver source codes locate in multiple
directories (such as under osd/, engine/, and cam/), how to write the
Makef
Hi guys:
Need your helps again! The following is a Makefile template for a device
driver in FreeBSD. But when my driver source codes locate in multiple
directories (such as under osd/, engine/, and cam/), how to write the
Makefile? I have tried but still can not get through this, please give me
On Mon, 21 Nov 2005, Maxime Henrion wrote:
Albert Vest wrote:
On Sat, 19 Nov 2005 01:58:25 +0200 (EET)
Vladimir Kushnir <[EMAIL PROTECTED]> wrote:
Hi all,
Is there any project on FreeBSD wrapper for ATI Linux drivers (like
nVidia's used to be)? If so - I'd be more than happ
Maxime Henrion wrote:
Albert Vest wrote:
On Sat, 19 Nov 2005 01:58:25 +0200 (EET)
Vladimir Kushnir <[EMAIL PROTECTED]> wrote:
Hi all,
Is there any project on FreeBSD wrapper for ATI Linux drivers (like
nVidia's used to be)? If so - I'd be more than happy to test (sorry I c
Albert Vest wrote:
> On Sat, 19 Nov 2005 01:58:25 +0200 (EET)
> Vladimir Kushnir <[EMAIL PROTECTED]> wrote:
>
> > Hi all,
> > Is there any project on FreeBSD wrapper for ATI Linux drivers (like
> > nVidia's used to be)? If so - I'd be more than happ
On Sat, 19 Nov 2005 01:58:25 +0200 (EET)
Vladimir Kushnir <[EMAIL PROTECTED]> wrote:
> Hi all,
> Is there any project on FreeBSD wrapper for ATI Linux drivers (like
> nVidia's used to be)? If so - I'd be more than happy to test (sorry I can
> hardly write it myself).
Hi all,
Is there any project on FreeBSD wrapper for ATI Linux drivers (like
nVidia's used to be)? If so - I'd be more than happy to test (sorry I can
hardly write it myself).
Regards,
Vladimir
___
freebsd-hackers@freebsd.org mailing
he driver author as to what
: criteria is used to bid/accept vs reject a function. Almost all drivers
: look at the pci device id set. Looking at merely the PCI class code is
: not recommended since it it far too ambiguous.
Generally speaking this is true. However, the class is available for
ins
rashmi ns wrote:
Hello All,
While writing a pci-driver for hdlc controller which has two functions
1.BRIDGE
2.Network
Do we need to write two separate drivers for each class-code or how can a
single driver manage two different functionalites .Are there any examples on
pci-multifunction
Hello All,
While writing a pci-driver for hdlc controller which has two functions
1.BRIDGE
2.Network
Do we need to write two separate drivers for each class-code or how can a
single driver manage two different functionalites .Are there any examples on
pci-multifunction drivers .I read in the
Sam Pierson wrote:
Hey guys,
In a current project, I need to find out exactly how long it takes to send
a 802.11 packet and how much time is spent in the following stages:
send time - time spent constructing message, including context switches
and other delays and the time it takes to transfer
Hey guys,
In a current project, I need to find out exactly how long it takes to send
a 802.11 packet and how much time is spent in the following stages:
send time - time spent constructing message, including context switches
and other delays and the time it takes to transfer the message to the
ne
Jason Tsai wrote:
> First sorry for my poor writing engish! I don't know if it's right to
> post in this mailist, but I think it's best place I can ask this kind
> of question.
>
> I am using FreeBSD 5.4-RC3 now for testing purpose, I find that if I
> use ifconfig_sis0="inet 10.10.1.148 netmask
Hi all,
First sorry for my poor writing engish! I don't know if it's right to post in
this mailist, but I think it's best place I can ask this kind of question.
I am using FreeBSD 5.4-RC3 now for testing purpose, I find that if I use
ifconfig_sis0="inet 10.10.1.148 netmask 255.255.255.0" in
"Anton Wöllert" <[EMAIL PROTECTED]> writes:
> i want to edit the syscons driver for additional vesa-support. but i don't
> want to rebuild the whole kernel every time i add a few new lines or a
> function. is there a way to just build the syscons object file and maby a
> few dependencies every time
> want to rebuild the whole kernel every time i add a few new lines or a
If you use config(8) to configure your kernel in the "traditional way",
this should come for free.
See:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html
_
On Sat, Dec 18, 2004 at 02:09:05PM +0100, "Anton Wöllert" wrote:
> Hello,
>
> i want to edit the syscons driver for additional vesa-support. but i don't
> want to rebuild the whole kernel every time i add a few new lines or a
> function. is there a way to just build the syscons object file and mab
Hello,
i want to edit the syscons driver for additional vesa-support. but i don't
want to rebuild the whole kernel every time i add a few new lines or a
function. is there a way to just build the syscons object file and maby a
few dependencies every time and then just link it together with the res
Hi.
I have two question. I hope what someone helps me.
First:
I have NVidia fx5600 and installs drivers from
/usr/ports/x11/nvidia-driver
# cat /boot/loader.conf
hw.ata.ata_dma=0
nvidia_load="YES"
linux_load="YES"
I am working on learning to write device drivers mainly because I have
no 3d on my system. After ready the handbooks and lots of source code I
have a question about the current driver I am trying to work on. Here
is a sample that I have a question about:
struct agp_nvidia_softc {
struct
i386/FreeBSD-4.x/lkm.
How does one get into 'realmode' inside a kernel driver?
The reason for the need is a tight timeing loop that measures the lenght of
pulses. And disableing interrupts is just not enough.
Target cpu's are AMD K5 + AMD XP.
Asfair when reading cycles per opcode. The number of
In message: <[EMAIL PROTECTED]>
Mark Murray <[EMAIL PROTECTED]> writes:
: "M. Warner Losh" writes:
: > The problem with decoupling things entirely from the drivers is that
: > many drivers will say "if I have this revision of that card, do this
: > w
"M. Warner Losh" writes:
> The problem with decoupling things entirely from the drivers is that
> many drivers will say "if I have this revision of that card, do this
> workaround." or "if I'm this or newer, I have this feature" both of
> which
7; might be, which would be sufficient.
The problem with decoupling things entirely from the drivers is that
many drivers will say "if I have this revision of that card, do this
workaround." or "if I'm this or newer, I have this feature" both of
which are broken by the kernel fo
ing at the mess in FreeBSD device drivers and how the drivers
decide to attach to a device or not, then a lot of effort would
be needed to clean those up, but should an alias file such as the
solaris one exist in FBSD, IMHO it would make the life of everyone
much easier.
Perhaps you should look into
Hi, FreeBSD hackers!
Is there some ongoing work on drivers for [EMAIL PROTECTED] and other DVB cards from
http://www.pentamedia.com? Any efforts to port Linux drivers?
If no, what DVB card is preferable for production use with FreeBSD?
TNX,
--
WBR, Alex Lukin,
RIPE NIC HDL: LEHA1-RIPE
On 27-Jun-2003 Thomas Moestl wrote:
>> Doing it in the bus might actually make life simpler. Right now
>> when using different tables for routing PCI interrupts on x86, I
>> have to write two different bridge drivers all
>> the time, one for host bridges and one for
&&
> >> pci_get_subclass(dev) == PCIS_BRIDGE_PCI)
> >> /* Routing across a child bridge. */
> >> else
> >> /* Routing a direct child that is not a bridge. */
> >
> > This leaves two possible probl
a direct child that is not a bridge. */
>
> This leaves two possible problems: first, there are other types of
> bridges (we currently support PCI-ISA and PCI-EBus ones, cardbus might
> also work) for which we need to use PCIB_ROUTE_INTERRUPT(); that could
> likely be dealt w
es, cardbus might
also work) for which we need to use PCIB_ROUTE_INTERRUPT(); that could
likely be dealt with by not testing the subclass at all.
More importantly, however, a bridge might want to allocate an
interrupt for itself; for example, cardbus bridge drivers do this to
handle insertion/eject
On 27-Jun-2003 Thomas Moestl wrote:
> On Fri, 2003/06/27 at 13:37:00 -0400, John Baldwin wrote:
>> On 13-Jun-2003 Thomas Moestl wrote:
>> > This requires us to get this firmware property in the OFW PCI bus
>> > driver before routing the interrupt; that can't be done in the pcib
>> > route_interrup
On Fri, 2003/06/27 at 13:37:00 -0400, John Baldwin wrote:
> On 13-Jun-2003 Thomas Moestl wrote:
> > This requires us to get this firmware property in the OFW PCI bus
> > driver before routing the interrupt; that can't be done in the pcib
> > route_interrupt method, since we don't know whether we ar
it is a method so that derived
> PCI bus drivers can override it.
>
> This is very useful for the sparc64 OFW PCI bus driver which I will
> commit soon, hopefully. On sparc64, there are some on-board devices
> which have special interrupt lines. To route their interrupts, we need
> n
1 - 100 of 494 matches
Mail list logo
