Release of IXJ driver for Quicknet LineJack/PhoneJack VoIP cards
Hi all, I have completed a port of the driver for Quicknet LineJack and PhoneJack cards from Linux to FreeBSD. www.quicknet.com These are telephony cards and feature - full duplex audio hardware - connenct a standard telephone handset - used for Video Conferencing or VoIP (with the OpenH323 ports) - a connected phone will ring when receiving a call and you can dial out too - comes with licenced audio codecs including G.723.1 - LineJack can be used with a telephone line and act as a PABX to VoIP gateway The driver can be found in the ports tree as a kld kernel loadable module in /usr/ports/comms/ixj I've tested it on my PCI PhoneJack. Devin Butterfield who initially did the port test it on his ISA PhoneJack. I've not got a LineJack to test. If anyone wants to try this out, please let me know and I can make sure everything is working for you. Once the driver is installed, you need to recompile OpenH323 and OhPhone to use the card. (or grab the new OpenH323_1.7.4_2 version of the port) Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://www.telepresence.strath.ac.uk 0141 548 2897 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Porting a Linux driver to FreeBSD with ioctl return values
Hi, > Yeah, that's basically what I had to do in tdfx. You can take > a look int src/sys/dev/tdfx/tdfx_pci.c under tdfx_ioctl(...) Great. Thanks for the pointer. I've just tested ioctl return values in some test code and it works ok. Thanks Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Porting a Linux driver to FreeBSD with ioctl return values
Hi, I'm porting the some linux telephony API drivers over to FreeBSD. But the author of the linux driver used the 'hack' of returning values from the ioctls as the error result. egvolume = ioctl (fd, IXJ_GET_VOLUME) instead of using error = ioctl (fd, IXJ_GET_VOLUME, &volume); Naturally I want to keep the API the same on FreeBSD so existing apps will compile without change. But right now it looks like I cannot do this. Is there anything I can do in the FreeBSD driver or in existing source to help, without imposing a new 'BSD' API. Cheers Roger Hardiman [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
AverMedia TV Card owner - IR Remote Specs obtained.
Hi, I've got the specs for the AverMedia IR Remote Control. I do not have any AverMedia hardware. So, I need some of you to do some simple programming and testing. And I do mean simple. No kernel drivers needed. FXTV needs a small change. Randall or myself can help. And I'll make the required change to the Bt848 driver. I've got the specs from a linux programmer who just made his code both GPL and BSD licence for us. What a nice guy. ( "Pawel T. Jochym" <[EMAIL PROTECTED]> ) So, anyone interested in helping? Roger -- Roger Hardiman [EMAIL PROTECTED] be his sample source code under the BSD licence too. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
IrDA InfraRed Drivers. Would anyone use them?
Hi, I'm thinking about porting some IrDA Infra Red drivers to FreeBSD. However, I'd like to know how many people would use this, if it is even worth it, and what devices you want to get to talk to each other. IrDA allows data exchange with the wide range of infra-red devices on the market including laptops, mobile phones and personal organisers. So, if you are interested, send me an email to [EMAIL PROTECTED] or just reply to this email. Once I've got a feel for the level of interest, I'll decide if this is worth following through. Cheers Roger -- Roger Hardiman [EMAIL PROTECTED] [EMAIL PROTECTED] -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://www.telepresence.strath.ac.uk 0141 548 2897 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Onboard Intel fxp network chip, unknown PHY 17 type 2
Hi > > However, it reports PHY Unknown type 17 addr 2. > Mike wrote: > This is just a diagnostic message; the interface ought to work > regardless. Have you tried it? Oops. It works. I can ping the machine next to me. Pass me the pointy hat. Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Onboard Intel fxp network chip, unknown PHY 17 type 2
David >Can you look on the motherboard and find out what type of chip it uses? > It should be one of: 82557, 82558, or 82559. Let me know. The lid is off. It says GD82559 I wonder if we can get Jordan to allow a quick commit fix for this one. The board (from SuperMicro) is a top end server board. Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Onboard Intel fxp network chip, unknown PHY 17 type 2
Hi, My new i840 chipset motherboard has onboard networking. It ises the Intel chipset and the FXP driver detects it. However, it reports PHY Unknown PHY 17 type 2. on the 4.0-current 2307 snapshot. Is there a quick fix for this? I'd really like to get networking going with this board. Thanks Roger -- Roger Hardiman [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Wanted: sound API experts for OpenH323 (NetMeeting for Unix) project
Hi, I need some help with the sound ioctls for the OpenH323 project. (OpenH323 can be called NetMeeting for Unix) OpenH323 is an Open Source H323 Video Conferening package, with full duplex audio and bi-directional video. It is ported to Linux and Windows, and can connect to a wide range of H323 compatible video conferencing programs, including NetMeeting. I'm working on the FreeBSD port and can now stream video from FreeBSD to NetMeeting and visa versa using our Bt848 driver. BUT... I need help with the audio ioctls. I've got all the linux source, but need to cook up FreeBSD audio code, especially for the full duplex audio. And I need some help. If you are interested, take a look at www.openh323.org and email me. I've got the latest source, not yet checked into the OpenH323 project wich fixes a few build errors on FreeBSD 3.4. It would be good to get this done in the next few days as it will make it onto the FreeBSD 4.0 release disks. Any helpers out there? Thanks Roger -- Roger Hardiman Bt848/Bt878 driver maintainer [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Multi Head XFree86 VGA card recomendations wanted
Hi, > > The Dual-Head G400 (the one in a single AGP card) does not > > work with XFree86. > > > It works fine with XFree86 using only one monitor output. Sorry, I was unclear with my last statement. The Dual-Head G400 is cannot be used with XFree86 as a Dual-Head card, but is great for use with a single monitor. Roger -- Roger Hardiman| Telepresence Research Group [EMAIL PROTECTED] | DMEM, University of Strathclyde tel: 0141 548 2897| Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557| http://www.telepresence.strath.ac.uk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Multi Head XFree86 VGA card recomendations wanted
> > I need to build some new Multi-Head FreeBSD machines > > in my lab using XFree86 3.9.16. > > > > I want to know which VGA cards to buy > > for Multi-Head (dual monitor) support. > > > matrox :) > > g200 / g400 > > you can buy dual-head cards, or use more than one card (pci only) The Dual-Head G400 (the one in a single AGP card) does not work with XFree86. XFree86 was written to support one monitor per VGA chip and cannot cope with 2 RAMDACs on one controller. Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Multi Head XFree86 VGA card recomendations wanted
Hi, I need to build some new Multi-Head FreeBSD machines in my lab using XFree86 3.9.16. I want to know which VGA cards to buy for Multi-Head (dual monitor) support. Currently I have 1 multi-head FreeBSD machine using Matrox Millenium cards abd XFree86 3.9.16. It works great, but you cannot buy Millenium cards any more. Reading the XFree86 docs, it seems almost all PCI cards are supported multihead on Linux where they can issue an INT 10 call to initialise the BIOS in the secondary card. I'm not sure it we can support that in FreeBSD. Cheers Roger -- Roger Hardiman| Telepresence Research Group [EMAIL PROTECTED] | DMEM, University of Strathclyde tel: 0141 548 2897| Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557| http://www.telepresence.strath.ac.uk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Help: SoundBlaster PCI 16, 64, 128, 64V, 128V revisions
Hi, I'm trying to list the full range of SoundBlaster PCI models. >From my research I have found the following Creative Labs models. CT4700 SB PCI 128 - (12 months ago) ES1370. 2 line outs for 4 speakers. Retail Box CT SB PCI 64V - unknown chip. 64 Value edition. 1 line out. OEM Market. CT4750 SB PCI 128V - unknown chip. 128 Value edition. 1 line out. OEM market. CT4740 SB PCI 16 - ES1373. 2 line outs for 4 speakers. Retail Box. 12 months ago, Creatives UK web site promoted the SB PCI 128 and the SB Live models. Today, they only promote the SB PCI 16 and SB Live models. Can those of you with SoundBlaster PCI cards help me fill out this table Thanks Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://www.telepresence.strath.ac.uk 0141 548 2897 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
HEADS UP: ES1371/1373 sound card support in -stable
Hi, I've just committed Russell Cattelan's patch for ES1371/ES1373 PCI Audio sound cards (which includes the new Creative Labs SoundBlaster 16, 64 and 128). This HEADS up is to explain that the code committed to -stable has not been committed to -current. This is because in 4.x-current, the PCM driver has been totally rewritten and so, the -stable driver and the -current driver are very very different. A commit to -current and an MFC are not applicable. If anyone experiences any problems with ES1370 sound cards or the new 1371 / 1373 support, please email Russell Cattelan <[EMAIL PROTECTED]> or Roger Hardiman <[EMAIL PROTECTED]> Thanks Roger -- Roger Hardiman [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 2 problems with the linksys mx driver
Hi, Problems with linksys (mx driver) cards in -stable and - current >>If I type in ifconfig mx0 media 100basetx >>it all works OK. >> >> Do you have any ideas on these. > >Autonegotiation is failing. That happens in the Fast Ethernet world. >Buying better quality switches *may* help. ;^) Can you get any better than 3COM's top of the range stacks? Seriously though, in -stable there are 2 bugs with the linksys (mx driver) cards. 1) In if_mx, (and a few other drivers too for that mater) the driver probes the link and then selects the most suitable speed and mode (half or full duplex) The code picks 100BaseT4 as its first chose, then 100 Meg Full Duplex second, then 100 Meg Half duplex, then 10 Full Duplex, then 10 Half duplex. The Ethernet specs I have read say the official order should be 100 Meg Full Duplex FIRST, then 100base T4, then 100 Meg Half duplex, then 10 Full D then 10 Half D. 2) Even if my line was 100BaseT4, the if_mx driver should not be passing an invalid paremter to if_media, causeing if_media to panic with something along the lines of "invalid media type 0x28/0xff" if_mx should not select 100BaseT4 if the rest of the kernel cannot handle it. _OR_ it should be passing the right parameter to if_media. Then there are issues in -current, but lets fix -stable first. This is all a bit different to the Bt848 driver, so I could do with some help kernel hacking. Cheers Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
2 problems with the linksys mx driver
Hi Bill, I'm having quite a few problems with my linksys cards. I think most are caused because I'm connected to a switch rather than a simple hub. The cards are the new Version 2 cards (with Wake On Lan) and use the MX driver. 1) On 3.3-stable, the linksys mx driver detects my network connection to a 3COM switch as 100BaseT4. However, the kernel then panics because if_media cannot support media type 0x28. My workarond was to hack the kernel source for if_mx.c and stop it detecting 100BaseT4. It now detects 100Base Full duplex and works ok. 2) On 4.x-current, the linksys mx driver is connected to a Kingston 10/100 Switch. It does not detect a carrier on the network. If I do ifconfig mx0 media auto I see the 'link in use' and '100 Megs in use' LED on my switch go on for 2 seconds, then go off for 2 seconds, then go on for 2 seconds, then go off for 2 seconds. When the link is up, I can ping and use the network etc. When the link is down, I have no network connection. If I type in ifconfig mx0 media 100basetx it all works OK. Do you have any ideas on these. I'm willing to test patches on both -stable and -current and can swap switches too (swap the 3COM and the Kingston) Thanks Roger -- Roger Hardiman| Telepresence Research Group [EMAIL PROTECTED] | DMEM, University of Strathclyde tel: 0141 548 2897| Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557| http://www.telepresence.strath.ac.uk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Is there anything like #ifdef BSD
Hi, I'm working with someone porting linux code to FreeBSD. Actually, they want to port it to all BSDs. So, rather than having #if defined (FreeBSD) || defined (NetBSD) || defined (OpenBSD || defined (bsdi) I am looking for a #if defined (BSD) or #ifdef BSD Is there such a beast, and do the other BSDs have it too? If not, I'll just go for the nice and simple #if defined (FreeBSD) || defined (NetBSD) || defined (OpenBSD || defined (bsdi) #define BSD #endif in a global header file. Roger -- Roger Hardiman| Telepresence Research Group [EMAIL PROTECTED] | DMEM, University of Strathclyde tel: 0141 548 2897| Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557| http://www.telepresence.strath.ac.uk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Bt848 based server
Richard Puga wrote: > > Is there any way to use a bt848 as a web cam or streaming video server > through any format other than the metor .ppm > snapshots. Tom, who did the BSDi port, has written code to do this. We has a web cam up and running on his site. I'll grab the sources and put them on the Bt848 driver homepage. When they are there, I'll send another email with the URL Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Moving bt848 driver to /sys/dev/bktr
Hi, I want to move the Bt848 driver to /sys/dev/bktr Here is why. The Bt848 driver (bktr) is contained in one file (/sys/pci/brooktree848.c) and currently runs to about 7000 lines. I've broken the driver down into 4 smaller files which cleanly splits the functionality (tuner, audio, card probing, Bt848 programming) With all the new .c and .h files, the new Bt848 driver consists of about 9 files now instead of 1. Rather than commit 8 new files to /sys/pci I would rather move the whole lot to /sys/dev/bktr and keep them neatly in their own directory (just like all the USB files are in one place) Splitting the files up makes it easier to maintain, easier to understand and easier to update. So, does anyone see any problems with this? Thanks Roger -- Roger Hardiman| Telepresence Research Group ro...@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897| Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557| http://telepresence.dmem.strath.ac.uk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Moving bt848 driver to /sys/dev/bktr
Hi, I want to move the Bt848 driver to /sys/dev/bktr Here is why. The Bt848 driver (bktr) is contained in one file (/sys/pci/brooktree848.c) and currently runs to about 7000 lines. I've broken the driver down into 4 smaller files which cleanly splits the functionality (tuner, audio, card probing, Bt848 programming) With all the new .c and .h files, the new Bt848 driver consists of about 9 files now instead of 1. Rather than commit 8 new files to /sys/pci I would rather move the whole lot to /sys/dev/bktr and keep them neatly in their own directory (just like all the USB files are in one place) Splitting the files up makes it easier to maintain, easier to understand and easier to update. So, does anyone see any problems with this? Thanks Roger -- Roger Hardiman| Telepresence Research Group [EMAIL PROTECTED] | DMEM, University of Strathclyde tel: 0141 548 2897| Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557| http://telepresence.dmem.strath.ac.uk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Attn AVerMedia Bt878 owners
Hi, Attn AVerMedia owners of TV cards with Bt878's (sorry - not the 848 users) I've got the specs from AVerMedia which mean I can finally get the Tuner Type autoselected for your cards. If you have an AVerMedia card which is one of the newer ones with a Bt878, can you please email me. I do not have one myself and need some test beds for my new code before I commit it to -current. Cheers Roger -- Roger Hardiman Bt848/878 driver maintainer [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Attn AVerMedia Bt878 owners
Hi, Attn AVerMedia owners of TV cards with Bt878's (sorry - not the 848 users) I've got the specs from AVerMedia which mean I can finally get the Tuner Type autoselected for your cards. If you have an AVerMedia card which is one of the newer ones with a Bt878, can you please email me. I do not have one myself and need some test beds for my new code before I commit it to -current. Cheers Roger -- Roger Hardiman Bt848/878 driver maintainer ro...@cs.strath.ac.uk ro...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
CVSWEB not happy with $FreeBSD$ change (was $Id$)
Hi, I've just done a commit following peters $Id$ to $FreeBSD$ changes. But CVSWEB is getting things totally wrong. Take a look at this URL, which points to the picoBSD 'build' script http://www.freebsd.org/cgi/cvsweb.cgi/src/release/picobsd/build/build?rev=1.18 The file is version 1.18, comitted by me (roger), but the web page gives the entry for 1.17, committed by Peter A cvs checkout on freefall gives the correct version and correct ID string. But the cvsweb pages is all messed up. Any ideas? Roger To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Help with exit status in shell script
Hi,
There is a bug in the PicoBSD build shell script in and I have no idea
how to fix it. As a result, build errors are not caught.
It is all to do with Exit Status of programs called from a shell script.
Please help.
The code fragment from /usr/src/release/picobsd/build/build is
./stage1 2>&1 | tee stage1.out
if [ "X$?" != "X0" ] ; then
echo "^G"
echo "-> ERROR in \"${i}\" script. Aborting the build process."
exit 10
fi
Build calls Stage1. Stage1 will return with an error code in some cases
and we want to trap this and halt the Build script.
./stage1 2>&1 | tee stage1.out
if [ "X$?" != "X0" ] ; then
Normally, $? will return the Exit Status of the last executed program.
However, due to the pipe through Tee, the Exit Status I get is the
exit status of Tee and not the exit status of the Stage1 script.
I still want to output the stage1 script to screen and a log file.
How can I do this and preserve the exit status for the Build script.
Thanks
Roger
--
Roger Hardiman
ro...@freebsd.org
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
CVSWEB not happy with $FreeBSD$ change (was $Id$)
Hi, I've just done a commit following peters $Id$ to $FreeBSD$ changes. But CVSWEB is getting things totally wrong. Take a look at this URL, which points to the picoBSD 'build' script http://www.freebsd.org/cgi/cvsweb.cgi/src/release/picobsd/build/build?rev=1.18 The file is version 1.18, comitted by me (roger), but the web page gives the entry for 1.17, committed by Peter A cvs checkout on freefall gives the correct version and correct ID string. But the cvsweb pages is all messed up. Any ideas? Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Help with exit status in shell script
Hi,
There is a bug in the PicoBSD build shell script in and I have no idea
how to fix it. As a result, build errors are not caught.
It is all to do with Exit Status of programs called from a shell script.
Please help.
The code fragment from /usr/src/release/picobsd/build/build is
./stage1 2>&1 | tee stage1.out
if [ "X$?" != "X0" ] ; then
echo "^G"
echo "-> ERROR in \"${i}\" script. Aborting the build process."
exit 10
fi
Build calls Stage1. Stage1 will return with an error code in some cases
and we want to trap this and halt the Build script.
./stage1 2>&1 | tee stage1.out
if [ "X$?" != "X0" ] ; then
Normally, $? will return the Exit Status of the last executed program.
However, due to the pipe through Tee, the Exit Status I get is the
exit status of Tee and not the exit status of the Stage1 script.
I still want to output the stage1 script to screen and a log file.
How can I do this and preserve the exit status for the Build script.
Thanks
Roger
--
Roger Hardiman
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
new device driver
Hi, A friend (Juha) has written a new device driver for another batch of video capture cards from LifeVide, Genoa and ATIech which use the Zoran and Philips SAA chipset. The driver is likely to be called ztv If I add this to FreeBSD, where is the best place Keep it in /usr/src/sys/pci Or add it to /usr/src/sys/dev/... perhaps /usr/src/sys/dev/pci/ztv What are we doing now with new PCI device drivers? Thanks Roger -- Roger Hardiman ro...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
new device driver
Hi, A friend (Juha) has written a new device driver for another batch of video capture cards from LifeVide, Genoa and ATIech which use the Zoran and Philips SAA chipset. The driver is likely to be called ztv If I add this to FreeBSD, where is the best place Keep it in /usr/src/sys/pci Or add it to /usr/src/sys/dev/... perhaps /usr/src/sys/dev/pci/ztv What are we doing now with new PCI device drivers? Thanks Roger -- Roger Hardiman [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: do softupdates work on SMP -stable and -current now?
Well, following up to my own post, 3 people have reported no problems with softupdates on their SMP machines. One was softupdates only 2 were softupdates and vimun together. Thanks for everyones prompt replies. Right, back to those PicoBSD commits. Bye Roger To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
do softupdates work on SMP -stable and -current now?
Hi, I remember reading in the mailing lists how softupdates were unreliable on SMP 3.x and -current machines about 6-8 months ago. Is this all fixed now for SMP machines? I've been using softupdates on a uni-processor 3.2-stable machine and it works well. I wanted to try it on my two SMP machines (one has 3.2-stable, one has -current) Bye Roger -- Roger Hardiman| Telepresence Research Group ro...@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897| Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557| http://telepresence.dmem.strath.ac.uk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
KLD bt848 driver and vm_page_alloc_contig
Hi, Is there a way to fix vm_page_alloc_contig() so it can allocate contiguous memory once userland has got up and running and memory has been fragmented/filled. I've finished porting the bt848 driver to the newbus framework. You can load/unload the driver with kldload and kldunload. Great for testing. Load test, unload, recompile, repeat... However, the driver needs about 2 meg of contiguous memory allocating. It must be contiguous as hardware writes directly into it. (same applies to the meteor driver and probably some of the sound card drivers) I can start X, and load the 'bktr' driver. But once I run a few apps, and memory fills up, I can no longer allocate the contiguous memory required. Clearly the kernel would need to swap out user process memory pages to make room for the contigous memory vm_page_alloc_contig() requires. Can this be done? Bye Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://telepresence.dmem.strath.ac.uk 0141 548 2897 ro...@cs.strath.ac.uk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Announcing vbidecode, videotext and Teletext
Hi, Recently I added VBI capture support to the Brooktree 848/878 driver (/dev/vbi0) This allows Teletext/Videotext capture and viewing. To complement this I have now added 'vbidecode' and 'videotext' to the ports collection /usr/ports/misc 'vbidecode' lets to decode teletext pages and save them to disk as .vtx files. There is one file for each page / sub-page 'videotext' lets to view/print/save to GIF and PNG the saved .vtx files. It also allows background searching of all teletext pages on disk. Instructions are a bit complicated at this time, but I suggest you read the Teletext instructions at http://telepresence.dmem.strath.ac.uk/bt848 In addition, there is Juha's ASCII .vtx file viewer at http://qn-lpr2-98.quicknet.inet.fi:22/stuff/vtxview.c Good luck Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://telepresence.dmem.strath.ac.uk 0141 548 2897 ro...@cs.strath.ac.uk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
IR Remote for AverMedia and FlyVideo
Hi, Several people have asked my recently about supporting the AverMedia remote control and the FlyVideo Remote Control units for their Bt848/Bt878 TV cards. Well, I finally got a reply from AverMedia and after checking on the Linux Infra Red Controller (LIRC) web site, I found the source and specs for the AverMedia and FlyVideo IR modules. I do not have AverMedia or Flyvideo hardware, so I'm not going to look into it, but if owner/hackers of these cards want to knock something up for the Bt848 driver, I'll gladly add it in along side the Hauppauge IR support we already have. Bye Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://telepresence.dmem.strath.ac.uk 0141 548 2897 ro...@cs.strath.ac.uk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: How to find the PCI chipset type inside a driver
David, > Just out of curiosity - every now-and-then, when watching TV with my > bt848 - the machine will lock up hard.. Lockups are a possibility with older motherboards where the PCI bus gets overloaded, or on some older SIS, VIA and OPTi motherboards where they did not implement the PCI spec properly when it comes to bus mastering. (the broken SiS/VIA chipsets toggle the PCI control lines incorrectly) Obviously Brooktree decided that SIS and VIA chipsets were sufficiently broken to add extra compatibility hardware into the Bt878 and Bt879. The Bt848 has the MYSTERY_BIT (see the source), which is not defined in the datasheets, but Brooktree told us to set it! It enables the Bt848's 430FX compatibilty mode and a small performance hit. So, your lockups could be due to either a PCI bus saturation or due to an old chipset. To avoid saturation, grab smaller image sizes. That worked for me on my very old VIA chipset embedded systems. Max grab size of 320x256 is stable. You may get better results from changing your BIOS PCI settings. Try turning OFF some of the PCI speedups, like combined writes. This seemed to help one person's stability. Ayway, I still want the driver to determine the motherboard PCI bus chipset for itself. Bye Roger To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
PCI bus chanages from 2.2.x to 3.x/4.x and data corruption.
Please read this. It affects our commercial users. I'm trying to find out if/how we initialise the PCI bus and any memory controllers differently in 3.x compared to 2.2.x Since upgrading from 2.2.x to 3.x or 4.x, many many users have noticed garbage on the video grabbed by the bt848 in their Video Conferencing systems. (based on VIC). This has been noticed by some commercial users of FreeBSD as well as Academic users, and it looks bad on us. Luigi has 1 PC with 2 hard disks, a 2.2.x setup and a 3.x setup. This allowed him to factor out all the variables except the 2.2.x kernel and the 3.x kernel. (He used the same Bt848 driver) On 2.2.x VIC runs great. On 3.x there is corruption to the video. Can people who have worked on the PCI bus, changes to bus mastering, perhaps changes to the IDE code (to enable bus mastering) or anything which may influence this get in tough. I posted this problem months ago and got little responce. This is hurting our customers! Bye Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://telepresence.dmem.strath.ac.uk 0141 548 2897 ro...@cs.strath.ac.uk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: How to find the PCI chipset type inside a driver
Dave >Just a thought - not really an answer to your question... but... > >I struck me that since bt848 isn't in the default kernel (you have >to build your own kernel for it) - couldn't you just make this >a flag in the config file? > >Then, a couple of #ifdef's in the bt848 driver would handle it. Actually, this is how I have implemented it. I have just commited to -current. Great minds think alike. :-) FYI, the linux bt848/bt878 driver is able to probe around and work out for itself that it is on an old triton 430fx board. Bye Roger To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
How to find the PCI chipset type inside a driver
Hi, I need the bt848/bt878 driver to find out the motherboard's PCI chipset. IE, Is this Bt878 card sitting on a VIA, SIS, OPTi or INTEL motherboard. Can this be done? The Bt878 can be programmed to run in "Intel (Full PCI2.1 ompatible) Mode" "Intel 440FX mode" "SIS/VIA/OPTi" mode. Each mode drives the PCI bus mastering slightly differently to cater for bugs/features in various PCI chipsets. Setting the Bt878 to SIS/VIA/OPTi mode fixed some strange machine hangs experienced by a UK user yesterday. I'd like the Bt848 driver to inquire about the PCI bus. To get the VENDOR and DEVICE_ID codes. It can then automatically enable the right mode on Bt878 chips. Any ideas? Ideally I need a method for 2.2.x, 3.x and -current. Bye Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://telepresence.dmem.strath.ac.uk 0141 548 2897 ro...@cs.strath.ac.uk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
error 6: panic : cannot mount root(2) with PicoBSD current
Help I'm trying to get the PicoBSD code on -current compiling again as it has got a bit stale. But I get a kernel Panic. I brought the kernel config files up to date. Booting with the 'dial' disk (build without ssh) panics with error 6: panic: cannot mount root (2) This comes just ater the sio and ie0 probes. I wonder if it has anything to do with the old entry config kernel root on wd0 which the new config program ignores. Any suggestions? Bye Roger To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: 3.2-RELEASE and netscape problem.
Jordan K. Hubbard wrote: > > > It breaks because compat22 is installing _everything_ in > > /usr/lib/compat/aout. We've reproduced this locally - compat22 is > > hosed. > Hmmm. Good thing I took that out of the default list of installation targets > then. :) > I tend to think that the compat22 distro simply aged and died but nobody > noticed > until now. :( Can we put anything on the 2 boot floppies. How about putting ld.so on one of the floopy disks and hacking the install program to always copy the ld.so file from floppy to /usr/libexec Then everyone gets a working system. However, installing the linux netscape 4.08 is a workaround I suppose the problems will be in Netscape and my XiGs Accel X 4.1. Anything other native FreeBSD aout binaries? Bye Roger To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
do you have any bt848 hacks (eg channel sets)
Hi, Do you have any bt848 driver hacks to the brooktree848.c source code you need to get the card working for you. eg audio mux changes Tuner frequency channel sets This DOES NOT include any kernel config options or any 'sysctl' options I'm looking for actual source code changes. I'm trying to make sure the bt848 driver is up to date. I've just spent time helping someone work out the Australian channel sets for the driver, only to be emailed by someone else who already worked them out. I'm trying to avoid this repetition. send emails to me at ro...@cs.strath.ac.uk Bye Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://telepresence.dmem.strath.ac.uk 0141 548 2897 ro...@cs.strath.ac.uk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: 3.2-RELEASE and netscape problem.
Jordan K. Hubbard wrote: > > > I installed it both during installation and then > > again via /stand/sysinstall just to make sure. > > > > Still no luck. > > Hmmm. So much for that idea. :) Oddness.. I copyied /usr/libexec/ld.so from my 2.2.7 machine to my 3.2 machine and it all worked. bye roger To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: 3.2-RELEASE and netscape problem.
Mike > > You will probably need the compat22 distribution for Netscape to work > correctly. I installed it both during installation and then again via /stand/sysinstall just to make sure. Still no luck. Bye Roger To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
3.2-RELEASE and netscape problem.
I have a fresh installation of FreeBSD 3.2 on my laptop. I tried to install netscape 4.08 from both ports and then as a package. Both times, I get the following error Couldn't load /usr/libexec/ld.so. It has been suggested I need to compile XFree86 locally. My poor laptop will take ages to do this. Not sure I have enough space either. Bye Roger -- Roger Hardiman To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
