video cd reading on freebsd (fwd)
-- Forwarded message -- Date: Sat, 14 Oct 2000 15:13:21 +0200 (CEST) From: Heiko Schaefer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], Soren Schmidt [EMAIL PROTECTED], Valeriy E. Ushakov [EMAIL PROTECTED] Subject: video cd reading on freebsd Hey everyone, as many of you might know (by reading -multimedia), i would like to write a video cd input plugin for xine (xine.sourceforge.net, a player for mpeg-1 and mpeg-2 video that is mainly developed on linux, which synchronizes playback of video and audio) that works on freebsd. the current video cd plugin for linux uses the linux ioctls, which we obviously don't have on freebsd (aside from luoqi's patch that is not in -stable, as far as i understand). it needs a way to read the toc of the vcd (which is a ioctl call on linux), and read the video stream off of the disc. i understand that there is a (quite straightforward) way to read the raw data off a video cd using an atapi drive and that Mike Meyer is going to make it work for scsi as well as soon as he has time to do that. now i still don't quite understand how to do read data off of video cds exactly (although probably the answer is in mails on -multimedia, which i intend to read through again looking for this information - after getting an atapi drive). if someone (uwe?) could send me some sample c-program that does that, i would be really grateful. but i have absolutely no clue about how to read the toc off a video cd. will sys/cdio.h's ioc_read_toc_entry work for that ? if so, will it work for atapi, scsi or both ?! Heiko To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: load average, to small to be true..
* Per Hallström NV98ATe [EMAIL PROTECTED] [001014 06:57] wrote: It seems I'm the only one that has discovered that FreeBSD (i have tried up to 4.1-RELEASE) dosen't want the load to be more than 1024, or maybe the only one that thinks it's annoying.. =) Why? I know FreeBSD can run more processes than that - I have tried with about 7000, running at the same time... too bad I can't see an impressive load average... It can't be that much extra work for the kernel to hold just some extra bits to support load averages that is far beyond reality, can it? You probably want to rase maxusers in your kernel config. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: yet another unsupported PHY in fxp driver
On Fri, Oct 13, 2000 at 11:21:45AM -0700, Paul Saab wrote: Dennis ([EMAIL PROTECTED]) wrote: Do you have any info on the "version 8" 82559 part (I assume you have access to docs online or otherwise)? New MBs that we just got in have this part and the messages have resurfaced. The docs for the etherexpress pro/100 are only available from Intel under NDA these days and they will not allow you to release *any* drivers if you sign it. Sounds like time to un-recommend Intel cards.. -- Wilko Bulte [EMAIL PROTECTED] Arnhem, the Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: yet another unsupported PHY in fxp driver
At 02:45 PM 10/13/2000, David Greenman wrote: The primary problems that have resulted in the "unsupported PHY" messages in the past year or so have been related to either the format or size of the SEEPROM changing. Using generic MII code doesn't fix the problem; the fxp's would still not work due to the MAC address being wrong, among other things, which is also read from the SEEPROM. This said, I think it is generally the right approach to use a generic MII PHY software interface and at some point the driver will likely be updated for that. It is low priority, however, since it doesn't solve any problems. Do you have any info on the "version 8" 82559 part (I assume you have access to docs online or otherwise)? New MBs that we just got in have this part and the messages have resurfaced. If you could point me at what to look for I'll try and tackle it and forward the info to you. without docs its a futile effort. I'm sure it's just like all the other 82559 parts, with perhaps some new features that we won't take advantage of (due to not having the documentation). If there is something useful indicated in the 'unsupported PHY" message that you mentioned (a type, for example), then it could easily be added. The 82559 has an integrated 82555 PHY, so I really doubt there is actually a new PHY to deal with. nope, type 0, addr 0. does this indicate (perhaps) another size change? Dennis Emerging Technologies, Inc. - http://www.etinc.com ISA and PCI T1/T3/V35/HSSI Cards for FreeBSD and LINUX Multiport T1 and HSSI/T3 UNIX-based Routers Bandwidth Management Standalone Systems Bandwidth Management software for LINUX and FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
ASUS CUBX Motherboard 3rd and 4th IDE channels
Hello. I am attempting to install FreeBSD 4.1.1, off floppy, brand new CUBX motherboard with the 4 IDE channels. It's a GENERIC kernel, so I've done nothing to it yet. The ata driver apparently does not recognize the 3rd and 4th IDE channels. I can find nothing in dmesg that even remotely looks like ata2 and ata3. Is there support for 4 IDE channels (i.e. 8 devices) in 4.1.1? (If not, take heart that the bios config does not even seem to recognize that there are 4 channels. I'm going to try to find a BIOS upgrade...) -- Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] The opinions expressed above are entirely my own "What lies behind and what lies before us are small matters compared to what lies within us." -Ralph Waldo Emerson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: yet another unsupported PHY in fxp driver
I'm sure it's just like all the other 82559 parts, with perhaps some new features that we won't take advantage of (due to not having the documentation). If there is something useful indicated in the 'unsupported PHY" message that you mentioned (a type, for example), then it could easily be added. The 82559 has an integrated 82555 PHY, so I really doubt there is actually a new PHY to deal with. nope, type 0, addr 0. does this indicate (perhaps) another size change? It indicates that something is wrong with the SEEPROM. Is it a SuperMicro motherboard? If so, they changed the layout in the SEEPROM. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ASUS CUBX Motherboard 3rd and 4th IDE channels
On Sat, Oct 14, 2000 at 12:59:40 -0700i, Dave Hayes wrote: Hello. I am attempting to install FreeBSD 4.1.1, off floppy, brand new CUBX motherboard with the 4 IDE channels. It's a GENERIC kernel, so I've done nothing to it yet. GENERIC: device ata0at isa? port IO_WD1 irq 14 device ata1at isa? port IO_WD2 irq 15 notice the lack of ata2 and ata3. I have no idea what irq to use though. The ata driver apparently does not recognize the 3rd and 4th IDE channels. I can find nothing in dmesg that even remotely looks like ata2 and ata3. Is there support for 4 IDE channels (i.e. 8 devices) in 4.1.1? (If not, take heart that the bios config does not even seem to recognize that there are 4 channels. I'm going to try to find a BIOS upgrade...) -- _ Patrick Seal|"Microsoft isn't evil, they just make [EMAIL PROTECTED] | really crappy operating systems." Hyperhost - http://www.hyperhost.net| -Linus Torvalds To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
PCI secondary bus
While writing the new cardbus code, I ran into a problem where certain BIOSes (Dells in particular) does not initialize the pci configuration space of the pci to cardbus bridge. On a "normal" laptop, the BIOS will fill in a memory address, irq lines, and the secondary and subordinate bus numbers. On a dell laptop, those would be left as 0. I could work around the memory/irq issues, but I have no clue what to fill in for the secondary and subordinate bus numbers. Is there a magical function (in kernel, pcibios or otherwise) that would generate these values for me? And if not, how do I get the numbers? Would it be alright if I assign an arbitrary number as long as there is no conflict? Any help would be appreciated. Thanks. -- (o_ 1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2 _o) \\\_\Jonathan Chen [EMAIL PROTECTED] /_/// ) No electrons were harmed during production of this message ( ~ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
