| : When my laptop is booting (Toshiba with ToPIC97, NoteWorthy modem,
| : LinkSys modem card) something odd happens:
| :
| : IP packet filtering initialized, divert disabled, rule-based forwarding
| : disabled
| : , default to accept, unlimited logging
| : pccard: card inserted, slot 0
| :
| In -current look at /boot/device.hints. In stable this is still in
| the kernel config file.
Is the hints file going to become standard, or is it just a tool to
help developers writing drivers for -current?
jm
--
My other computer is your windows box.
To Unsubscribe: send mail to [EMAIL
| : Is the hints file going to become standard, or is it just a tool to
| : help developers writing drivers for -current?
|
| It is standard in current, so in 5.0-release and newer people will
| have to cope.
So the idea is that drivers will be modules dynamically loaded based on
the hints
On Tue, Feb 12, 2002 at 10:33:25AM -0700, M. Warner Losh wrote:
| In message: [EMAIL PROTECTED]
| j mckitrick [EMAIL PROTECTED] writes:
| : So the idea is that drivers will be modules dynamically loaded based on
| : the hints file?
|
| Not currently. But someone could come in and do
| It isn't a huge effort conceptutally, but there is a lot of
| infrastructure that CardBus depends on that isn't in -stable or only
| partially MFC'd. If someone wanted to start cranking on it, they
| could get it done in a few weeks worth of work.
Where would be a good place to start?
jm
--
Thanks, Warner!
On Mon, Feb 11, 2002 at 09:37:08AM -0700, M. Warner Losh wrote:
| NEWBUS:
| The current way of doing FreeBSD device configuration. This
| is approximately sys/kern/subr_bus.c, bus_if.m and device_if.m.
That part is pretty clear.
| CardBus:
| PCMCIA standard for PCI
Some commits have been in the tree for a month now, and I'm wondering if
anyone has had any problem. Please let me know if you have had any
timeouts, mode recognition problems, or anything similar. It would be nice
to get the commits moved into -stable if everything is working well,
especially
On Sat, Jul 07, 2001 at 12:00:19PM -0700, David O'Brien wrote:
| On Fri, Jul 06, 2001 at 11:52:05PM +0100, j mckitrick wrote:
| I get version 1.15. When I look at the .c,v file in the cvs tree, it says
| HEAD is 1.16, but $Id says it is 1.15.
|
| We don't use $Id$ anymore. Do you mean
I'm *sure* I'm doing something wrong here, but I can't figure it out.
I am using cvsup to keep a -current cvs tree on my system. According to
the web access cvs tree, a file I am looking at should be version 1.16.
When I try
cvs -R co -f src/sys/dev/ppbus/immio.c
I get version 1.15. When I
On Thu, Apr 05, 2001 at 03:32:23AM -0700, Julian Elischer wrote:
| try teh sample driver in /usr/share/exaples/drivers/make_device_driver.sh
Perfect! Just what I was looking for. Thanks.
jm
--
---
Jonathon McKitrick -- [EMAIL
Could someone point me to a device that is well-written, follows newbus, and
would be a good example of how a device driver should be written?
thanks,
jm
--
---
Jonathon McKitrick -- [EMAIL PROTECTED]
"It took the
Hi all,
I have been working with Nicholas Souchu to fix a few issues with the
parallel port zip, especially the zip+ (250 meg version).
I know this is deprecated hardware, but I would like to know if it helps.
The driver should now work correctly in PS2 transfer mode, which in theory
should be
On Wed, Aug 23, 2000 at 06:14:46PM +0200, Soren Schmidt wrote:
| Well, "work" is exactly the word to use, they work on *some* chipsets
| with *some* drivers, but they have problems there as well. Remember
| that most wintel boxes doesn't even use DMA...
really? why is that? and why include the
A friend of a friend asked me to find out how ATA66 support was coming
along. Is it still necessary to disable DMA or PIO settings for it to work?
jm
--
-
Jonathon McKitrick -- [EMAIL PROTECTED]
"The physicist's greatest
hi all,
i have been working with nicholas souchu to fix the parallel port zip drive
bug. we think we have it beat. however, nicholas doesn't have a devbox, so
he has asked me if someone could contact me for the corresponding fix. i
have a few minor details to ask him about, and he will then
I saw this link recently...
http://home.zonnet.nl/vanrein/badram/
Apparently, you make a floppy with the supplied image, boot with it to
find the bad RAM addresses, and then those addresses are passed on as a
kernel parameter once the patch is applied. Bad addresses will be excluded
from
Does anyone recall seeing or making a remark about a group of interrupts or
hardware port locations that could be causing this problem? I was searching
my email and i can't find it.
Someone said 4.0 allocates a group of hardware locations (0x380-0x3f0?)
differently from 3.4, and that this may
I'm not sure if this belongs on -stable or -current. Has anyone taken
a look at the timeout problem in the parallel port zip driver?
jm
--
Jonathon McKitrick -- [EMAIL PROTECTED]
Pure... unrefined... spice
On Thu, Mar 23, 2000 at 11:46:57AM -0500, Sean O'Connell wrote:
J McKitrick stated:
I'm not sure if this belongs on -stable or -current. Has anyone taken
a look at the timeout problem in the parallel port zip driver?
Have you tried backing vpo.c down to 1.19 (1.20 was committed
on 23
Here is a concern i have. I had a hard time getting my parallel port
zip to work under 3.4. It turned out there may be a bug in my bios
that required me to change from EPP mode to standard bi-directional.
Walter noted that EPP mode worked OK for him under 3.4, but did not
under -current. Oddly
Will NIBBLE mode still be supported in 4.0? Has anyone tried a ZIP drive with bios
set at ECP or
standard setting? I would like to know what to expect if i upgrade.
--
-= jm =-
---
Student Loan Officer: "Mr. Wright? We'd like to know what
21 matches
Mail list logo
