Re: Where to find docs on newbus vs. cardbus vs. newcard
| : 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 | : pccard: card inserted, slot 1 | : pccard: card removed, slot 1 | : pccard: card inserted, slot 0 | : pccard: card inserted, slot 1 | | That's odd. | | : You can see slot 1 acts like it was removed and reinserted. To make it | : even more interesting... | | You are right. | | : Mounting root from ufs:/dev/ad0s1a | : sio1 at port 0x2f8-0x2ff irq 11 flags 0x4 slot 0 on pccard0 | : sio1: type 16550A | : sio1: unable to activate interrupt in fast mode - using normal mode | : ed1 at port 0x240-0x25f iomem 0xd4000-0xd7fff irq 11 slot 1 on pccard1 | : ed1: address e2:0c:0f:05:6d:54, type NE2000 (16 bit) | : | : You can see the NIC comes up as ed1. This used to be ed0 around 4.3, | : IIRC. Is this related to the problems with slot 1 under ToPIC97? | : I could be wrong, but I believe my modem used to be sio0 as well. I | : remember having to change it in my ppp script after a build world some | : time ago. | | Maybe hints consume ed0 and sio0 likely. So, the game is afoot! Is there anything I can do to help track this down? jm -- My other computer is your windows box. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
| 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 PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
| : 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 file? jm -- My other computer is your windows box. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
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 that project. Hint, hint. :-) No pun intended. Well, I helped convert a few of the ppbus drivers to modules, maybe I could help? jm -- My other computer is your windows box. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
| 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 -- My other computer is your windows box. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
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 cards in the PC Card form factor.
I was pretty close on this as well. These are specifically 32-bit
cards, correct?
| dev/{pccard,pcic,exca,cardbus,pccbb}/*. I'm in the process of fixing
| bugs in this code base as well as removing redundant code and
| expanding support for more bridges and client devieces. This is what
| I've been calling NEWCARD.
Ah, this was the part I got mixed up. I thought Newcard was already up
and running with the last iteration of changes you made (remember me and
ToPIC on Toshiba? ;-) I thought this was already in -stable.
jm
--
My other computer is your windows box.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
any problems with parallel port zip drives?
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 since 4.4 will be coming up soon. jcm -- o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o | Jonathon McKitrick ~ | | I prefer the term 'Artificial Person' myself. | o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: conficting cvs version numbers?
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 $FreeBSD$? If so, please try | to be more exact. Also try ``cvs status'' on the file. My mistake. I was just using generic terminology. Well, according to status, I *do* have the latest version. But here is the confusing part. I have 1.16 of the file locally In the web CVS repository, $FreeBSD$ expands to version 1.16 In my local version, $FreeBSD$ is expanded to version 1.15 What could explain this? p.s. I just downloaded the file from the web repository and diff'ed it with the one in my local directory: local:~ diff immio.c /sys/dev/ppbus/immio.c 27c27 * $FreeBSD: src/sys/dev/ppbus/immio.c,v 1.16 2001/06/23 06:51:51 nsouch Exp $ --- * $FreeBSD: src/sys/dev/ppbus/immio.c,v 1.15 2001/01/25 13:07:55 nsouch Exp $ local:~ Jonathon -- Microsoft complaining about the source license used by Linux is like the event horizon calling the kettle black. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
conficting cvs version numbers?
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 look at the .c,v file in the cvs tree, it says HEAD is 1.16, but $Id says it is 1.15. The same string expanded in the web cvs tree says 1.16. It seems I am always one behind, even though HEAD in the cvs file reflects the -current version. What silly mistake am I making? Jonathon -- Microsoft complaining about the source license used by Linux is like the event horizon calling the kettle black. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: newbus driver code
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 PROTECTED] "It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here." --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newbus driver code
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 computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here." --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
parallel port zip+ fix
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 twice as fast as NIBBLE mode. Set the flags for ppc to 0x00, so the driver will detect all available modes and choose the best one. Probing and mode selection has been much improved, thanks to Nicholas' work. If you want to force PS2 mode, that should work as well. Please let me know if you have any problems. jcm -- o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o | Jonathon McKitrick ~ | | "I prefer the term 'Artificial Person' myself." | o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA66 support
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 feature if it is not used by the biggest segment of the market? | Besides it seems as if its our much more agressive usage thats the | real problem, looks like firmware problems too me how is bsd more aggressive (other than the obvious buildworld load)? maybe we should go easier on the hardware for real-world compatibility and reliability reasons? jcm -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATA66 support
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 tool is his wastebasket." - Albert Einstein - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
parallel port zip patch - committer needed
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 contact you with the patch. jm -- --- Jonathon McKitrick -- [EMAIL PROTECTED] To Microsoft: "Your tyranny I was part of, is now cracking on every side. Now your own life is in danger. Your Empire is on fire." Front 242 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
bad memory patch?
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 addressable/virtual memory from then on. Sounds like sometheing we could use, eh? jm -- --- Jonathon McKitrick -- [EMAIL PROTECTED] To Microsoft: "Your tyranny I was part of, is now cracking on every side. Now your own life is in danger. Your Empire is on fire." Front 242 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Parallel port zip drives - inventory of working and non-working systems
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 affect the parallel port allocation on laptops. Has anyone had this zip timeout error on a desktop machine and not been able to fix it? jm -- --- Jonathon McKitrick -- [EMAIL PROTECTED] To Microsoft: "Your tyranny I was part of, is now cracking on every side. Now your own life is in danger. Your Empire is on fire." Front 242 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
parallel zip driver problem
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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: parallel zip driver problem
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 Jan). There was also a fairly large commit on 14 Jan. Have you emailed the author (nsouch)? No, and no. I'm not quite sure about how to 'back out' changes. But the real reason i didn't take a similar approach is because someone else i am corresponding with about this said the vpo code doesn't seem to be the culprit. He thinks it's the da code, possibly. And once he started wading around in that, he said it's been gutted, so he felt a quick fix would be unlikely. I should email the author, however. jm -- Jonathon McKitrick -- [EMAIL PROTECTED] Pure... unrefined... spice To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Parallel port Zip drive and EPP mode
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 enough, EPP mode worked fine under win95, so there doesn't seem to be some innate incompatiblity between my laptop and Zip drives in EPP mode. Is this worth looking into? -- -= jm =- --- The opinions expressed in this message are the opinions of the mail program only, and not of the writer, his employer, or freebsd-uk.eu.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Paralle mode ZIP support
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 you did with the $30,000 dollars we gave you for college." Steven Wright: "I gave it to my friend Bob, and he built a nuclear weapon with it. And i'd really appreciate it if you didn't call me anymore." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
