libarchive/bsdtar snapshot available
A fairly complete snapshot of libarchive and bsdtar, including source code, complete documentation, and some background about why I'm doing this and what I hope to accomplish is now available: http://people.freebsd.org/~kientzle/libarchive/ It needs a lot of testing still, but is getting to the point that someone other than me should be able to make sense of it. ;-) Feedback appreciated. Tim Kientzle [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Atmel WLAN Driver
In message: <[EMAIL PROTECTED]> "Daan Vreeken [PA4DAN]" <[EMAIL PROTECTED]> writes: : (to stop cross-posting please 'cc' follow-ups to -questions) : : On Monday 22 December 2003 19:10, Markus Kovero wrote: : > Hi. I Have Belkin 11MBps wlan adapter F5D6020 ver.2 that uses atmel : > chipset. I noticed that support for freebsd hasnt been made yet but I : > found leenox driver for it. So I thought to ask would it be possible to : > port leenox driver to freebsd so I could use my wlan pcmcia card. : > Linux driver I found: http://atmelwlandriver.sourceforge.net/news.html : I have been (and still am) working on a FreeBSD driver for the USB version of : this adapter. The driver homepage can be found here : : http://vitsch.net/bsd/atuwi/ : : If you want to try to get the PCMCIA version working, you could have a look at : the driver to start with, since the device itself is the same, only the : interface to it is different. OpenBSD has wi driver that does both PCMCIA and USB versions of the prism-2 chipset. I suspect that something similar here would be a good thing. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Per CPU region of memory
On Tue, 2003-12-23 at 02:23, Aniruddha Bohra wrote: > Hello, > I am writing a loadable kernel module where I > need a per-cpu region of wired memory. The module should > work for -current and -stable. > > How can I get such a region of memory? > Any docs or pointers would be great. Try looking at contigmalloc (in sys/vm/vm_contig.c) -- Seeya...Q -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _ / Quinton Dolan [EMAIL PROTECTED] __ __/ / / __/ / / /__ / _// / Gold Coast, QLD, Australia __/ __/ __/ / / - / Ph: +61 419 729 806 ___ / _\ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pci_cfgintr: can't route an interrupt ...
[Drop my IPv6-only address for any replies, or hostname-only for IPv4...] There was a thread about this in this list back in late may of 2003. I recently found a mainboard which exhibits this problem with one particular card I have -- a combi OHCI+EHCI USB card with firewire, and an on-card HiNT PCI-PCI bridge. This card worked mostly fine on a probably-older DEC Venturis machine. A roughly-same-age-as-the-found-board machine was tried before the boot- time interrupt storm was discovered and solved with -stable months ago, so I can't say how well it worked there. I can only quote from a NetBSD boot somewhat later in this message. I'm using FreeBSD-4 with hacked source from around September-ish right now, and here's part of the verbose boot on the ``new'' found machine that has this problem (166MHz Pentium)... bios32: Found BIOS32 Service Directory header at 0xc00fb950 bios32: Entry = 0xfbdd0 (c00fbdd0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xbe00 pnpbios: Found PnP BIOS data at 0xc00fcab0 pnpbios: Entry = f:cad8 Rev = 1.0 Other BIOS signatures found: ACPI: [...] pcib1: at device 10.0 on pci0 found-> vendor=0x1033, dev=0x0035, revid=0x41 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=12 map[10]: type 1, range 32, base d000, size 12 found-> vendor=0x1033, dev=0x0035, revid=0x41 class=0c-03-10, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=b, irq=255 map[10]: type 1, range 32, base d0001000, size 12 found-> vendor=0x1033, dev=0x00e0, revid=0x02 class=0c-03-20, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=c, irq=255 map[10]: type 1, range 32, base d0002000, size 8 found-> vendor=0x1106, dev=0x3044, revid=0x46 class=0c-00-10, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=12 map[10]: type 1, range 32, base d0003000, size 11 map[14]: type 1, range 32, base e000, size 7 pci1: on pcib1 ohci0: mem 0xd000-0xdfff irq 12 at device 8.0 on pci1 using shared irq12. usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered [...] ohci1: mem 0xd0001000-0xd0001fff at device 8.1 on pci1 pci_cfgintr: can't route an interrupt to 1:8 INTB ohci1: Could not allocate irq device_probe_and_attach: ohci1 attach returned 6 pci1: (vendor=0x1033, dev=0x00e0) at 8.2 fwohci0: port 0xe000-0xe07f mem 0xd0003000-0xd00037ff irq 12 at dev ice 11.0 on pci1 I'm able to use ohci0 as well as fwohci0; ohci1 and the ehci controller get irq=255 which -STABLE doesn't seem to be able to handle. On the other old machine, where it works, IRQs are assigned as shown: bios32: Found BIOS32 Service Directory header at 0xc00fff70 bios32: Entry = 0xfc716 (c00fc716) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x246 pnpbios: Found PnP BIOS data at 0xc00f5870 pnpbios: Entry = f:ae95 Rev = 1.0 Other BIOS signatures found: ACPI: [...] pcib1: at device 11.0 on pci0 found-> vendor=0x1033, dev=0x0035, revid=0x41 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base fcfff000, size 12 found-> vendor=0x1033, dev=0x0035, revid=0x41 class=0c-03-10, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=b, irq=10 map[10]: type 1, range 32, base fcffe000, size 12 found-> vendor=0x1033, dev=0x00e0, revid=0x02 class=0c-03-20, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=c, irq=9 map[10]: type 1, range 32, base fcffdc00, size 8 found-> vendor=0x1106, dev=0x3044, revid=0x46 class=0c-00-10, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base fcffd000, size 11 map[14]: type 1, range 32, base fc80, size 7 pci1: on pcib1 ohci0: mem 0xfcfff000-0xfcff irq 11 at device 8.0 on pci1 [...] ohci1: mem 0xfcffe000-0xfcffefff irq 10 at device 8.1 on pci1 ehci0: mem 0xfcffdc00-0xfcffdcff irq 9 at de vice 8.2 on pci1 [...] fwohci0: port 0xfc80-0xfcff mem 0xfcffd000-0xfcffd7ff irq 11 at dev ice 11.0 on pci1 using shared irq11. As I said, it appears to work without problem, though just before I swapped that old machine for the found board, I lost function of the USB mouse after many days of working flawlessly together with firewire disk activity, which problem I didn't bother to track down since it was the first time any such thing has happened to me. As I noted, I also tried this card under NetBSD many months ago on a motherboard of roughly the same vintage. Here's what NetBSD had to say at boot about it on that machine: BIOS32 rev.
cvsup hanging
I am having a problem with cvsup on a fresh install of 5.1-RELEASE. After running cvsup -g -L 2 src-supfile the program does nothing after "Parsing supfile..." If I intentionaly make the supfile malformed, i.e. removing the *default release=cvs line, cvsup will go past "Parsing supfile..." and give me the appropriate error. I have heard their are odd quicks with file permissions, so I exactly mirrored my new setup with a know good system running -CURRENT. The supfile permissions are 644 and the /usr/local/etc/cvsup/sup directory has perms of 755, both owned by root:wheel (and I run cvsup as root.) I also suspected their could be a problem with the connection, as it appears that my system sends out a DNS lookup when I run cvsup. Telnetting to cvsup2.freebsd.org on port 5999 is no problem. I am behind a firewall, but I set it to be wide open for troubleshooting this problem. I also tried plugging in the IP address of several cvsup servers. Running cvsup-without-gui 16.1h with supfile: *default host=cvsup2.freebsd.org compress *default release=cvs *default base=/usr/local/etc/cvsup *default prefix=/usr *default delete use-rel-suffix *default tag=. src-all _ Grab our best dial-up Internet access offer: 6 months @$9.95/month. http://join.msn.com/?page=dept/dialup ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
status of modem on inspiron 8500
Greetings all, I am curious as to the status of the integrated modem on the dell inspiron 8500. I'm sure someone will say no one cares about a dial up modem anymore but it always happens that one is on the road and dial up is the only access one can get. Any information on progress on this drive would be useful. I believe this is the dmesg entry for it: pci0: at device 31.6 (no driver attached) -James ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Atmel WLAN Driver
(to stop cross-posting please 'cc' follow-ups to -questions) On Monday 22 December 2003 19:10, Markus Kovero wrote: > Hi. I Have Belkin 11MBps wlan adapter F5D6020 ver.2 that uses atmel > chipset. I noticed that support for freebsd hasnt been made yet but I > found leenox driver for it. So I thought to ask would it be possible to > port leenox driver to freebsd so I could use my wlan pcmcia card. > Linux driver I found: http://atmelwlandriver.sourceforge.net/news.html I have been (and still am) working on a FreeBSD driver for the USB version of this adapter. The driver homepage can be found here : http://vitsch.net/bsd/atuwi/ If you want to try to get the PCMCIA version working, you could have a look at the driver to start with, since the device itself is the same, only the interface to it is different. > Thanks. > Peaceful xmas and happy newyear! Greets Markus Kovero grtz, Daan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Per CPU region of memory
Hello, I am writing a loadable kernel module where I need a per-cpu region of wired memory. The module should work for -current and -stable. How can I get such a region of memory? Any docs or pointers would be great. Thanks Aniruddha ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Atmel WLAN Driver
Hi. I Have Belkin 11MBps wlan adapter F5D6020 ver.2 that uses atmel chipset. I noticed that support for freebsd hasnt been made yet but I found leenox driver for it. So I thought to ask would it be possible to port leenox driver to freebsd so I could use my wlan pcmcia card. Linux driver I found: http://atmelwlandriver.sourceforge.net/news.html Thanks. Peaceful xmas and happy newyear! Greets Markus Kovero ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: support for __thread
On Sun, 21 Dec 2003, Alfred Perlstein wrote: > Any idea of how much effort it would take? I have no clue as to > how to fix our toolchain, gooing the work in ld.so doesn't see > that awful, but it's not trivial either: > > http://people.freebsd.org/~alfred/tls.pdf > > I want a threaded webstone so that I can generate a lot more load > with wimpier client boxes on FreeBSD. While you're working on gcc / our linker, you may want to investigate this article that I just saw on news.google.com as well: --- GCC summit in Kuwait concludes meetings, approves ''anti-terrorism'' agreement --- I'm not sure exactly what OS support that requires, but having it would certainly put us ahead of OpenBSD's ProPolice + nonexec stack! Mike "Silby" Silbersack ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: support for __thread
On Mon, 22 Dec 2003, Dan Nelson wrote: > In the last episode (Dec 22), Daniel Eischen said: > > I'd like to stay away from maintaining libc_r any further; not that > > it can't be done, but with libkse and libthr around, why? > > Do gdb and pstack (in ports) handle libkse or libthr threads? libc_r I don't know what pstack is, but we should have gdb for 5.3R. > is a great debugging tool, if nothing else. I can't even attach to a > libkse-threaded program with gdb; the tracee gets SIGSTOP'ped, and gdb > just sits there. You have to kill -9 gdb from another tty, and the > tracee dies. gdb can attach to a libc_r program, view all the threads, > and detach without affecting the tracee. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: support for __thread
Alfred Perlstein wrote: Well yes, but first would be getting the toolchain to emit proper code... It'd help but the linker is where all the action happens.. Marcel seems to understand this quite well. I can give the ld.so work a shot if someone gives me a general idea of how to get at the linker sets and registers in C code. WHen you have read and understood the document that describes the __thread implementation then I guess the next step would be to read and understand ld (and the rt version). It would be nice if it worked with libc_r as well, is there any chance for that? Webstone doesn't need kernel threads really... the relatively lightweight nature of libc_r doing strictly network IO makes it an attractive solution for what I'm trying to accomplish. Once it has been done for libpthread then it is almost free for libc_r because in libc_r we can set %gx once and forget it and just change the address it points to whenever we schedule a different thread. -- ++ __ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ [EMAIL PROTECTED] +-->x USA\ a very strange | ( OZ)\___ ___ | country ! +- X_.---._/presently in San Francisco \_/ \\ v ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB link cables.
Has anyone looked into supporting USB link cables? I see a number of these on eBay ... they appear to have two usb host connectors and some small bit of electronics (by the description). Are these propriatary ... or is there some sensible way this would work? Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
