On Mon, 09 Jan 2012 19:56:47 -0600, Hiroki Sato wrote:
This is an expected behavior. ACCEPT_RTADV is disabled by default on
9.X.
Thanks for clarifying. I'll make sure I update our documentation at work
regarding how exactly to get ACCEPT_RTADV working so this is clarified.
Regards,
ult on
9.X.
fe> I try forcing via the sysctl: net.inet6.ip6.accept_rtadv=1
fe>
fe> Still doesn't work!
This needs a reboot. Did you reboot the box?
fe> Why? What makes this machine different? All the other machines I run
fe> do not require this to get ACCEPT_RTADV. Is
other machines I run do
not require this to get ACCEPT_RTADV. Is it the re driver? My other
machines have em and ath interfaces.
Thanks,
Mark
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
Mark Felder wrote
in :
fe> On Sat, 07 Jan 2012 14:23:46 -0600, Hiroki Sato
fe> wrote:
fe>
fe> > It is an unexpected behavior and the flag should be set on all
fe> > interfaces. Can you send me your /etc/rc.conf, /etc/sysctl.conf, and
fe> > the result of "ifconfig -a"?
fe>
fe> Back at work
On Sat, 07 Jan 2012 14:23:46 -0600, Hiroki Sato wrote:
It is an unexpected behavior and the flag should be set on all
interfaces. Can you send me your /etc/rc.conf, /etc/sysctl.conf, and
the result of "ifconfig -a"?
Back at work so I have access to the machine again:
rc.conf:
hostname="
Mark Felder wrote
in <891fe25c-1560-479f-b855-1713c1c7a...@email.android.com>:
fe> Hiroki Sato wrote:
fe> >
fe> > Is it correct that ACCEPT_RTADV option was enabled on the vboxnet0
fe> > and not on re0, even after setting net.inet6.ip6.accept_rtadv to 1 at
fe> > boot time and ipv6_activate_all
Hiroki Sato wrote:
>
> Is it correct that ACCEPT_RTADV option was enabled on the vboxnet0
> and not on re0, even after setting net.inet6.ip6.accept_rtadv to 1 at
> boot time and ipv6_activate_all_interfaces="YES"?
>
>-- Hiroki
Yes, that is the behavior I witnessed.
_
Mark Felder wrote
in :
fe> I figured I would end up putting that in rc.conf as a temporary fix,
fe> but maybe that's just the long term solution. It seems so odd to me
fe> that the sysctl change doesn't automatically cause the ACCEPT_RTADV
fe> option to show up for re0, but it does for vboxnet0
Looping in hrs@ because he's the author of those changes.
On 01/06/2012 11:35, Mark Felder wrote:
> On Fri, 06 Jan 2012 12:49:45 -0600, Sergey Kandaurov
> wrote:
>
>>
>> You mean ipv6_activate_all_interfaces="YES" ?
>>
> Yes... Unfortunately that's what I get for typing it manually and being
> d
On Fri, 06 Jan 2012 12:49:45 -0600, Sergey Kandaurov
wrote:
You mean ipv6_activate_all_interfaces="YES" ?
Yes... Unfortunately that's what I get for typing it manually and being
distracted at the time. :-)
What is in your rc.conf? Do you have "inet6 accept_rtadv" keyword in it?
IIRC it
re's the
> ACCEPT_RTADV???
> media: Ethernet autoselect (100baseTX )
> status: active
>
> I have to manually do
>
> # ifconfig re0 inet6 accept_rtadv
>
> to get it to work. Am I missing something? Grepping /etc/rc.d/ for rtadv
> finds no clues. Is
omething? Grepping /etc/rc.d/ for rtadv
finds no clues. Is this broken for everyone, for the re driver, or am I
just crazy?
Here's pciconf for the device -- let me know if any further info would be
useful:
re0@pci0:4:0:0: class=0x02 card=0x04f51028 chip=0x816810ec rev=0x06
On 12/15/10 4:33 AM, Dr. Baud wrote:
Is there a cap on the amount of memory a driver (via bus_dmamem_alloc) can
allocate, other than the obvious physical memory limit minus the memory already
allocated?
well it has to fit into the kernel virtual space too.
this is quite limited on x86 thou
In message <20100811203042.ga26...@modermoor.genua.de>, Hans-Joerg Hoexer wrote:
>Hi,
>
>On Wed, Aug 04, 2010 at 07:39:41PM +0900, Takanori Watanabe wrote:
>> Update my patch. Split bus attachment from main driver file
>> (need to update sys/conf/files), add detach method for convinience,
>> and a
In message <201008040347.o743leer046...@sana.init-main.com>, wrote:
>Quick review and hack:
>
>1.How about attaching it as acpi child driver?
>
>In some case, TPM may appear in ACPI namespace (with _HID) and
>TPM spec defines ACPI method to handle TPM specific request.
>
>2. Is identify method need
In message <20100802120236.gb29...@modermoor.genua.de>, Hans-Joerg Hoexer wrote:
>Hi,
>
>we have developed a driver tpm(4) for various TPMs for OpenBSD 4.7 and
>FreeBSD 8.0 and have ported and updated several third party packages to
>enable use of TPMs on Open- and FreeBSD. This enables applicatio
In message: <[EMAIL PROTECTED]>
"Alex Hornung" <[EMAIL PROTECTED]> writes:
: 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 th
On Wed, 2006-12-06 at 11:35 -0500, John Baldwin wrote:
...
> I don't see why this patch changes things. devclass_delete_device() only
> clears dev->unit, dev->devclass, and dev->nameunit. device_set_driver()
> doesn't check or clear any of those. In fact, your change does make
> device_set_dr
On Wednesday 29 November 2006 18:18, Iasen Kostoff wrote:
> Hi,
> It seems that after I load and then unload a driver its name stays
> linked to the device e.g:
>
> [EMAIL PROTECTED]:10:0: class=0x068000 card=0x81411043 chip=0x005710de
> rev=0xa3
> hdr=0x00
>
> but of course if_nfe is neither
In message <[EMAIL PROTECTED]>, "M. Warner Losh" wrote:
>takawata-san,
>
>I have looked over this patch, and it looks good to me. Will you have
>time to commit it soon, or would you like someone else to commit for
>you?
I'll commit it soon. Thanks.
___
takawata-san,
I have looked over this patch, and it looks good to me. Will you have
time to commit it soon, or would you like someone else to commit for
you?
Warner
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
On Sun, 8 Jan 2006 [EMAIL PROTECTED] wrote:
> I wrote a driver for it. http://www.init-main.com/ufoma.tar.gz>
WoW - thank you. This worked perfectly and out of the box (the
modem,vendor1) !
Would love to see this going into freebsd by default.
Dw.
_
On Sunday 20 November 2005 11:04 am, rashmi ns wrote:
> Hello List ,
>
> Thanks for the help you given me .
>
> We have written driver for hdlc controller .The kernel is crashing
> after unloading
> the module with trap 12 fault .here is the order in which we release the
> resources while detach
Hi, re:
> The problem that I am having
> right now is
> that I have a fairly nice graphics card which, for the moment is only
> supported on Windows Operating systems, and old 2.4 Linux kernels.
Someone mentioned X drivers; current X drivers are
dynamically loaded into the X server, which
2005/10/12, Scott Long <[EMAIL PROTECTED]>:
> Pete wrote:
> > Hello,
> >I have what may seem to be a silly question, but I cannot find any
> > other decent resources on the web. >.< The problem that I am having
> > right now is
> > that I have a fairly nice graphics card which, for the moment i
Sangwoo Shim wrote:
2005/10/12, Scott Long <[EMAIL PROTECTED]>:
Pete wrote:
Hello,
I have what may seem to be a silly question, but I cannot find any
other decent resources on the web. >.< The problem that I am having
right now is
that I have a fairly nice graphics card which, for the mome
In message: <[EMAIL PROTECTED]>
Scott Long <[EMAIL PROTECTED]> writes:
: For more detailed information, you'll need
: to dig into the kernel source code, look for appropriate manual pages,
: and ask questions. There are a number of really good people on this
: list that try to answer m
Pete wrote:
Hello,
I have what may seem to be a silly question, but I cannot find any
other decent resources on the web. >.< The problem that I am having
right now is
that I have a fairly nice graphics card which, for the moment is only
supported on Windows Operating systems, and old 2.4 Li
On 10/11/05, Pete <[EMAIL PROTECTED]> wrote:
> Hello,
> I have what may seem to be a silly question, but I cannot find any
> other decent resources on the web. >.< The problem that I am having
> right now is
> that I have a fairly nice graphics card which, for the moment is only
> supported on
>From: Pete <[EMAIL PROTECTED]>
>Date: Tue Oct 11 11:47:28 CDT 2005
>To: freebsd-hackers@freebsd.org
>Subject: Driver Development Books?
>Hello,
>I have what may seem to be a silly question, but I cannot find any
>other decent resources on the web. >.< The problem that I am having
>right now
On Friday 25 February 2005 04:39 am, Peter Jeremy wrote:
> On Thu, 2005-Feb-24 17:59:19 -0700, Scott Long wrote:
> >- kernel option support. How do we support vendor modules in a kernel
> >that might be compiled with PAE (rather common these days), SMP, MAC,
> >etc. The loader and /boot infrastru
On Thu, 2005-Feb-24 17:59:19 -0700, Scott Long wrote:
>- kernel option support. How do we support vendor modules in a kernel
>that might be compiled with PAE (rather common these days), SMP, MAC,
>etc. The loader and /boot infrastructure has no concept of this. It's
>highly important, though.
A
On Fri, 25 Feb 2005 14:14, M. Warner Losh wrote:
> : I think PORTS_MODULES is a little suboptimal..
>
> How so?
If you upgrade your ports tree and then rebuild your kernel you may upgrade a
port KLD without wanting to.
> : Fx5200 Go). It also means that the kernel build/install does not result
>
[[ don't cc freebsd-hackers@ and hackers@ ]]
In message: <[EMAIL PROTECTED]>
"Daniel O'Connor" <[EMAIL PROTECTED]> writes:
: On Fri, 25 Feb 2005 12:39, M. Warner Losh wrote:
: > One does not need to patch the source tree at to pick up ports modules
: > for a kernel rebuild. One can bu
On Fri, 25 Feb 2005 12:39, M. Warner Losh wrote:
> One does not need to patch the source tree at to pick up ports modules
> for a kernel rebuild. One can build the ports modules as part of the
> kernel by simply defining PORTS_MODULES in a kernel config file. In
> addition, one can specify absolu
In message: <[EMAIL PROTECTED]>
Scott Long <[EMAIL PROTECTED]> writes:
: - runtime support. Where will modules be put, how will they be ensured
: to not collide with the base system modules, and how will the system
: ensure that they get loaded on every boot. Most of the pieces are in
[EMAIL PROTECTED] writes:
I updated the driver to be able to change wireless status, by
dev.acpi_tpkey.0.bluetooth,
dev.acpi_tpkey.0.wlan
sysctl value. (WLAN handling may not be correct.)
http://www.init-main.com/acpi_tpkey/acpi_tpkey.c
In message <[EMAIL PROTECTED]>, Niki Denev
wrote:
On my X31,
I updated the driver to be able to change wireless status, by
dev.acpi_tpkey.0.bluetooth,
dev.acpi_tpkey.0.wlan
sysctl value. (WLAN handling may not be correct.)
http://www.init-main.com/acpi_tpkey/acpi_tpkey.c
In message <[EMAIL PROTECTED]>, Niki Denev
wrote:
>On my X31, when i load acpi_tpkey a
[EMAIL PROTECTED] writes:
Hi, I updated ThinkPad Hotkey driver so that it can
* Read Brightness
* Read Volume
* Read Mute status
* Read Keylight status
* AccessIBM, Zoom Screen(Fn+Sp) toggle.
ToDo lists
* Set Brightness
* Set Volume
* Bluetooth attach/detach.
* Userland worker.
These features will
Takanori Watanabe wrote:
Hi, I updated ThinkPad Hotkey driver so that it can
* Read Brightness
* Read Volume
* Read Mute status
* Read Keylight status
* AccessIBM, Zoom Screen(Fn+Sp) toggle.
ToDo lists
* Set Brightness
* Set Volume
* Bluetooth attach/detach.
* Userland worker.
These features will c
On Mon, Aug 09, 2004 at 04:03:18AM +0200, Arne Schwabe wrote:
> IIrc correct the WLAN indicator is wired to the minipci for Thinkpads,
> at least the linux madwifi (which is basically our ath driver but our
> ath has not been updated for some very long time) has support for the
> IBM thinkpad wlan
[EMAIL PROTECTED] writes:
>
> * Wireless LAN indicator
>
> Will be take more time.
>
IIrc correct the WLAN indicator is wired to the minipci for Thinkpads,
at least the linux madwifi (which is basically our ath driver but our
ath has not been updated for some very long time) has support for the
On Tue, Mar 02, 2004 at 06:03:43AM -0500, [EMAIL PROTECTED] wrote:
> hello, i've got a question about the driver compilation. I finally wrote
> my driver, and i'm trying to compile it to test it. I tryed to use
> /usr/share/examples/drivers/make_device_driver.sh to build the whole
> stuff, but it d
In message: <[EMAIL PROTECTED]>
"Claudio Martella" <[EMAIL PROTECTED]> writes:
: Through the DEV_MODULE() macro i defined the loading routine and
: used DRIVER_MODULE() macro to define the pci driver.
: My first doubt is if
: it's legal to use both of them in the same file/driver. Sho
On 11-Nov-2003 Jason wrote:
> Here is the error:
>
> drm0: port 0xa000-0xa0ff mem
> 0xec02-0xec02,0xe000-0xe7ff irq 10 at device 0.0 on pci2
> info: [drm] Initialized radeon 1.9.0 20020828 on minor 0
> error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
>
In message: <[EMAIL PROTECTED]>
Bruce M Simpson <[EMAIL PROTECTED]> writes:
: Craig,
:
: On Sat, Nov 08, 2003 at 10:11:22PM -0500, Craig StJean wrote:
: > I have a prism2 USB wireless device. I've never written drivers before but I have
been developing for the past 8 years. Could some
Craig,
On Sat, Nov 08, 2003 at 10:11:22PM -0500, Craig StJean wrote:
> I have a prism2 USB wireless device. I've never written drivers before but I have
> been developing for the past 8 years. Could someone guide me to a website or
> something that would help me write a USB wrapper for the wi de
Hi,
>I'm currently developing a driver for this watchdog-card:
> 'Antrax WatchCard PCI' -> http://www.antrax.de/ (German)
>(btw. Antrax != Anthrax)
>
>And now I have some questions:
>
>- Should I develop the driver for 4.x or 5.x or both?
Cool !
That depends where do you plan to use it. I supp
in -current, we have a new netgraph node ng_device
that gives a device interface to netgraph.
We also have the ng_tty node that attaches to a tty
as a 'line disciplin'
adding a node between these to do you own stuff would give you what you
want.
(the ng_device node shuld be Merged from current s
On Wed, Oct 31, 2001 at 10:37:47AM -0800, Matthew Jacob wrote:
> "dumb" is relative and fungible.
Sure..
> It's a tradeoff between doing the connection management in firmware (as with
> the QLogic) or in the Kernel (as with Tachyon products mostly). It depends on
> whom you believe ultimately do
Matthew Jacob wrote:
>
> "dumb" is relative and fungible.
>
> It's a tradeoff between doing the connection management in firmware (as with
> the QLogic) or in the Kernel (as with Tachyon products mostly). It depends on
> whom you believe ultimately does a better job.
>
> Doing it in firmware al
"dumb" is relative and fungible.
It's a tradeoff between doing the connection management in firmware (as with
the QLogic) or in the Kernel (as with Tachyon products mostly). It depends on
whom you believe ultimately does a better job.
Doing it in firmware allows the driver writer to manage the
On Wed, Oct 31, 2001 at 09:49:19AM -0800, Matthew Jacob wrote:
That is probably what we call the Jaguar in-house. It is (IIRC) a
dumb adapter, there is a Tachyon on it for sure.
Wilko
> Yes, well, there is something Linux called the Compaq Fibre Channel Driver,
> and it's not QLogic based- nor
Yes, well, there is something Linux called the Compaq Fibre Channel Driver,
and it's not QLogic based- nor is it Emulex based- I believe it's Tachyon-
lite.
On Wed, 31 Oct 2001, Wilko Bulte wrote:
> On Wed, Oct 31, 2001 at 08:08:42AM +0100, Wilko Bulte wrote:
> > On Tue, Oct 30, 2001 at 06:04:1
On Wed, Oct 31, 2001 at 08:08:42AM +0100, Wilko Bulte wrote:
> On Tue, Oct 30, 2001 at 06:04:16PM -0600, Nick Rogness wrote:
>
> There is the isp(4) driver, by Matt Jacob, that supports Qlogic
> FC HBAs.
Further clarifyin this: CPQ use QL2200 for use with Linux.
CPQ KGPSA are Emulex LP[78]000,
On Tue, Oct 30, 2001 at 06:04:16PM -0600, Nick Rogness wrote:
There is the isp(4) driver, by Matt Jacob, that supports Qlogic
FC HBAs.
> The company I work for is willing to pay for someone to write a Compaq
> Fibe Channel driver for FreeBSD. Please write me personally if you are
> interested
In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: On Sat, Sep 15, 2001 at 12:13:58PM -0600, Warner Losh wrote:
: > In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: > : It is best to order this from largest to smallest size if you are worried
: > : about alignment holes, etc.
: > :
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes:
>On Sat, Sep 15, 2001 at 12:13:58PM -0600, Warner Losh wrote:
>> unfortunately, there are many device structures that are passed around
>> via DMA and hte like that don't let you do this...
>
>How come? The struct represents some [semi-]p
On Sat, Sep 15, 2001 at 12:13:58PM -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> "David O'Brien" writes:
> : It is best to order this from largest to smallest size if you are worried
> : about alignment holes, etc.
> :
> : int64_t d; /* 8-byte boundary */
> : int32_t c; /* 4-
In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: It is best to order this from largest to smallest size if you are worried
: about alignment holes, etc.
:
: int64_t d; /* 8-byte boundary */
: int32_t c; /* 4-byte boundary */
: int32_t f; /* 4-byte boundary */
: int
On Fri, Sep 14, 2001 at 12:23:44PM +0400, Yar Tikhiy wrote:
> E.g., will the following structure:
> struct foo {
> };
> contain alignment holes in any architecture/compiler?
It is best to order this from largest to smallest size if you are worried
about alignment holes, etc.
int64_t d; /
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : Any form of packing is going to cause problems for items that are
> : located in illegal fashions.
>
> It is almost more appropriate to use bus_space_{read,write} than using
> memory mapped structures. The bus macros will work for otherwis
In message <[EMAIL PROTECTED]> Mike Smith writes:
: Any form of packing is going to cause problems for items that are
: located in illegal fashions.
It is almost more appropriate to use bus_space_{read,write} than using
memory mapped structures. The bus macros will work for otherwise
unaligned
> On Thu, Sep 13, 2001 at 04:09:57PM -0700, Mike Smith wrote:
> > >
> > > Is there a single blessed way to define packed structures
> > > for use in drivers? I suspect that using "#pragma pack(1)"
> > > will lead to alignment errors in non-Intel architectures.
> >
> > Any form of packing is goi
Peter Wemm writes:
> The same goes for __format_arg(n) in stdio.h. And so on. We've been pretty
> clean about it so far, but a few have slipped through.
>
That __format_arg, btw, breaks the Compaq CCC compiler & causes us to
have to override stdio.h because of just that one line.
Does you
Terry Lambert wrote:
> Mike Smith wrote:
> > Having said that, I recommend using __attribute__ ((packed))
> > to explicitly request that a structure be packed.
>
> Is there a problem with "#pragma pack(1)"? I see it in a
> lot of header files... do they need changing?
Yes, but it should be:
#de
Mike Smith wrote:
> Having said that, I recommend using __attribute__ ((packed))
> to explicitly request that a structure be packed.
Is there a problem with "#pragma pack(1)"? I see it in a
lot of header files... do they need changing?
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
On Thu, Sep 13, 2001 at 04:09:57PM -0700, Mike Smith wrote:
> >
> > Is there a single blessed way to define packed structures
> > for use in drivers? I suspect that using "#pragma pack(1)"
> > will lead to alignment errors in non-Intel architectures.
>
> Any form of packing is going to cause pr
> Hi there,
>
> Is there a single blessed way to define packed structures
> for use in drivers? I suspect that using "#pragma pack(1)"
> will lead to alignment errors in non-Intel architectures.
Any form of packing is going to cause problems for items that are
located in illegal fashions.
Hav
> Hi there,
>
> Is there a single blessed way to define packed structures
> for use in drivers? I suspect that using "#pragma pack(1)"
> will lead to alignment errors in non-Intel architectures.
gcc deals with it, certainly on alpha anyway. However, I don't think
anyone would ever bless using
Nicolas Souchu wrote:
>
> On Tue, Mar 20, 2001 at 04:50:09PM +0100, Willem van Engen wrote:
> > I'm trying to write a module which should be a child of the smbus.
> > When I make the driver a child of the isa bus, identify, probe,
> > and attach functions are properly called. I use the following
>
On Tue, Mar 20, 2001 at 04:50:09PM +0100, Willem van Engen wrote:
> I'm trying to write a module which should be a child of the smbus.
> When I make the driver a child of the isa bus, identify, probe,
> and attach functions are properly called. I use the following
> code to do that:
> DRIVER_MO
"Matthew N. Dodd" wrote:
>
> On Wed, 21 Mar 2001, Willem van Engen wrote:
> > DRIVER_MODULE(smb, smbus, smb_driver, smb_devclass, 0, 0);
> > so I guess not. But thanks anyway :)
>
> Yes, but the 'smbus' bus driver doesn't have an attachment to your driver.
>
> You're trying to create a device t
In message <[EMAIL PROTECTED]>, Willem van Engen $B$5$s$$$o$/(B:
>> And you will need to know grandparent device name to bind the device
>> collectly.(Or should we need a way to get device attribute such as
>> Mother board, Video Capture BitBang,Video Capture Cooked,VGA Card and etc.)
>I don't
Takanori Watanabe wrote:
>
> In message <[EMAIL PROTECTED]>, Willem van Engen $B$5$s$$$o$/(B:
> >I'm trying to write a module which should be a child of the smbus.
> >When I make the driver a child of the isa bus, identify, probe,
> >and attach functions are properly called. I use the following
On Wed, 21 Mar 2001, Willem van Engen wrote:
> DRIVER_MODULE(smb, smbus, smb_driver, smb_devclass, 0, 0);
> so I guess not. But thanks anyway :)
Yes, but the 'smbus' bus driver doesn't have an attachment to your driver.
You're trying to create a device that provides an 'smbus' right?
Or did I
"Matthew N. Dodd" wrote:
>
> On Tue, 20 Mar 2001, Willem van Engen wrote:
>
> > I'm trying to write a module which should be a child of the smbus.
> > When I make the driver a child of the isa bus, identify, probe,
> > and attach functions are properly called. I use the following
> > code to do
On Tue, 20 Mar 2001, Willem van Engen wrote:
> I'm trying to write a module which should be a child of the smbus.
> When I make the driver a child of the isa bus, identify, probe,
> and attach functions are properly called. I use the following
> code to do that:
> DRIVER_MODULE(my, isa, my_dri
> I'm trying to write a module which should be a child of the smbus.
The smbus probe/attach is broken; you're going to have to fix it before
this code will work properly. 8(
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not
In message <[EMAIL PROTECTED]>, Willem van Engen $B$5$s$$$o$/(B:
>I'm trying to write a module which should be a child of the smbus.
>When I make the driver a child of the isa bus, identify, probe,
>and attach functions are properly called. I use the following
>code to do that:
> DRIVER_MODULE
It's currently working as an isa-child, but I'm still wondering
if it's the 'clean' way, since I only use smbus commands.
- Willem
Willem van Engen wrote:
>
> I'm trying to write a module which should be a child of the smbus.
> When I make the driver a child of the isa bus, identify, probe,
> a
* Jeff Brooke <[EMAIL PROTECTED]> [010126 21:37]:
> My questions are: (i) where, if at all, can I find info/tutorials/examples on
>driver-writing with this method? (ii) what are the benefits of the newbus method?
>(iii) is it still at all acceptable to write drivers using the old style/method?
At 10:32 AM 01/24/2001, David Rufino wrote:
>* Mike Smith ([EMAIL PROTECTED]) wrote:
> > > I am currently trying to port the compatability layer of a linux
> > > kernel driver to FreeBSD 4.x. The bit I'm stuck on at the moment
> > > is, how do I map arbitrary physical address space to kernel virt
* Mike Smith ([EMAIL PROTECTED]) wrote:
> > I am currently trying to port the compatability layer of a linux
> > kernel driver to FreeBSD 4.x. The bit I'm stuck on at the moment
> > is, how do I map arbitrary physical address space to kernel virtual
> > address space (ala ioremap() in linux) ? Th
> I am currently trying to port the compatability layer of a linux
> kernel driver to FreeBSD 4.x. The bit I'm stuck on at the moment
> is, how do I map arbitrary physical address space to kernel virtual
> address space (ala ioremap() in linux) ? Thanks.
You don't.
If this is a PCI device, it's
> On Sun, 23 Jul 2000, Mike Smith wrote:
>
> > > These adapters are OEMed by Dell as the PERC 2/QC and by HP as the HP
> > > NetRAID-4m.
>
> FWIW, I've got a plethora of 2450's and 4350's at work... I think some
> have the PERC 3, but I'll check tomorrow... and grab any with the PERC
> 2 (or
On Sun, 23 Jul 2000, Mike Smith wrote:
> > These adapters are OEMed by Dell as the PERC 2/QC and by HP as the HP
> > NetRAID-4m.
FWIW, I've got a plethora of 2450's and 4350's at work... I think some
have the PERC 3, but I'll check tomorrow... and grab any with the PERC
2 (or are the 2/3 mode
>
> The first BETA version of the 'aac' driver for the Adaptec AAC-364
> 'Jalapeno' and AAC-3642 'Jalapeno II' RAID adapters is available from
>
> http://people.freebsd.org/~msmith/RAID/index.html#adaptec
>
> These adapters are OEMed by Dell as the PERC 2/QC and by HP as the HP
> NetRAID-4m.
On Fri, 7 Jul 2000, Sergio Faustino wrote:
> To make the QuickCam (grayscale) work with Windows NT machines you
> must install an NT driver. I'd like to know as to get this driver.
Ask in a NT forum, then.
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www
89 matches
Mail list logo
