valgrind
hi, I found this tool called valgrind (http://devel-home.kde.org/~sewardj/) a few days ago and find it really interesting. It is something similair to purify (memory use debugger one could call it I guess) but GPL'ed and developed by the KDE team from what I can tell. I have been looking for this kind of tool for a long time and haven't found one I really like yet. As it is right now valgrind is x86linux 2.4 specific (probably gcc specific too..) but I would really love to see a FreeBSD port. It should be quite possible to port the OS specific parts to handle FreeBSD systemcalls instead of Linux ones. Is anyone already looking in to this or interested? It would be a great tool to debug the base system with as well as your own applications. -- ---. Patrik SundbergAddress: Rydsvägen 100C, 584 31 Linköping, Sweden | Email: [EMAIL PROTECTED] || [EMAIL PROTECTED] | Phone: +46 13 178567 || +46 707 602240| .--- Applied Physics and Electrical Engineering student | |- Master of Science in Business Administration and Economics student | |--- UNIX/Programming consultant | `--' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: valgrind
On Wed, Feb 27, 2002 at 11:00:14AM -0500, Matthew Emmerton wrote: I'm working on porting this right now. great news! what is the current status and have you set up a website for the project or will it be a simple portsentry with some patches? (I thought it would require some more rewriting than a usual port+patches, but I could be wrong, haven't looked at the code yet). Be forewarned, though, that the FreeBSD hacks for this tool will *never* be allowed into the main distro. Why? Licence. Valgrind includes some code from the Linux kernel and libc. When we hack it for FreeBSD, we'll end up putting some BSD-licenced code into a GPL product. Obviously, this will cause problems. as long as it can exist in the ports-collection I will be more than pleased. -- ---. Patrik SundbergAddress: Rydsvägen 100C, 584 31 Linköping, Sweden | Email: [EMAIL PROTECTED] || [EMAIL PROTECTED] | Phone: +46 13 178567 || +46 707 602240| .--- Applied Physics and Electrical Engineering student | |- Master of Science in Business Administration and Economics student | |--- UNIX/Programming consultant | `--' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Archos 6000
On Sat, Dec 01, 2001 at 09:40:33AM +0100, Bernd Walter wrote: On Thu, Nov 29, 2001 at 03:35:43PM -0800, Gregory Neil Shapiro wrote: ps has anyone tested using a Archos 6000 (using a isd200 interface) with the ps umass driver under freebsd? Just bought one (the 20G version but same interface) this weekend and can verify that it does not work with -STABLE. I also saw the Linux driver but I don't know the USB code at all. Hopefully, a USB-knowledgeable developer will port it out of the kindness of his or her heart. Does it get connectet to umass? If yes and you see read errors this should be just another quirk candidate. i found a posting on the netbsd current mailinglist stating that with some minor modifications it sort of attached to the umass driver, but the author had no further success. the posting can be viewed at: http://www.geocrawler.com/archives/3/497/2001/7/100/6233506/ hope someone with the right knowledge takes this one on :) -- ---. Patrik SundbergAddress: Rydsvägen 100C, 584 31 Linköping, Sweden | Email: [EMAIL PROTECTED] || [EMAIL PROTECTED] | Phone: +46 13 178567 || +46 707 602240| .--- Applied Physics and Electrical Engineering student | |- Master of Science in Business Administration and Economics student | |--- UNIX/Programming consultant | `--' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Archos 6000
has anyone tested using a Archos 6000 (using a isd200 interface) with the umass driver under freebsd? if it isn't working, is anyone working on getting it supported? there is a linux driver (http://bjorn.haxx.se/isd200/) but i don't really grok usb and the linux driver.. -- ---. Patrik SundbergAddress: Rydsvägen 100C, 584 31 Linköping, Sweden | Email: [EMAIL PROTECTED] || [EMAIL PROTECTED] | Phone: +46 13 178567 || +46 707 602240| .--- Applied Physics and Electrical Engineering student | |- Master of Science in Business Administration and Economics student | |--- UNIX/Programming consultant | `--' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
newpcm audio recording
Hi, I have been trying to do some audio-recording lately without much success. After searching the archieves etc I found some reports of this problem and there are also some PR's about it (8bit at low rates ok, 16bit and higher rates is not). I was wondering if someone is working on this and if we could expect some progress soon? -- Patrik Sundberg - email: [EMAIL PROTECTED] || [EMAIL PROTECTED] --- telefon: 013-178 567 - mobiltelefon: 070-760 22 40 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm audio recording
On Tue, Jan 09, 2001 at 02:29:59PM +0100, Erik H. Bakke wrote: Hi, I have been trying to do some audio-recording lately without much success. After searching the archieves etc I found some reports of this problem and there are also some PR's about it (8bit at low rates ok, 16bit and higher rates is not). I was wondering if someone is working on this and if we could expect some progress soon? I believe this may be related to the soundcard driver, which soundcard are you using? I am using an SB Live 1024 in my computer, and I am reading from the audio input, 16 bits at 44.1KHz, although only in mono, doing fourier transform on the data, and displaying the results graphically, without any problems. I have a SB32 isa-card. -- Patrik Sundberg - email: [EMAIL PROTECTED] || [EMAIL PROTECTED] --- telefon: 013-178 567 - mobiltelefon: 070-760 22 40 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA timeout errors
On Tue, Mar 14, 2000 at 12:17:15PM -0500, Will Saxon wrote: Hello, I think this may have already been presented/answered but I am not certain. I have noticed recently that every so often I will get the following set of messages, generally right after the bootup sequence finishes: ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA ad0: trying fallback to PIO mode ata0: resetting devices .. done This latest episode is on a 5.0-Current machine cvsupped yesterday, I got those messages while trying to log in after a reboot. I also get this when booting - think it started happening when I started using the new ata-driver. For me it happens when the root is supposed to be mounted (from dmesg): snip atapci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 snip ad0: 2015MB ST32132A [4095/16/63] at ata0-master using WDMA2 ad2: 814MB Maxtor 7850 AV [1654/16/63] at ata1-master using PIO3 acd0: CDROM CD820E.0v1098300 at ata0-slave using PIO3 Mounting root from ufs:/dev/ad0s1a ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA ad0: trying fallback to PIO mode ata0: resetting devices .. done and then everything proceeds as normal. I dont get any panics or anything, and after the reset to PIO everything seems to work fine. agree. ad0 is an IBM Deskstar 22GXP. I recall something about Deskstars resetting their heads every week as a possible explanation for a similar problem, is that what this is too? As you can see I am using a seagate disk and I am having the same problem. I would of course prefer to be in DMA mode all the time rather than PIO. If there is something I can do to fix this I'm all ears. There are probably many people out there affected by this so I really think it ought to be fixed - preferably before -RELEASE. -- Patrik Sundberg - email: [EMAIL PROTECTED] || [EMAIL PROTECTED] --- telefon: 013-178 567 - mobiltelefon: 070-760 22 40 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA timeout errors
On Tue, Mar 14, 2000 at 01:33:55PM -0800, Kris Kennaway wrote: On Tue, 14 Mar 2000, Patrik Sundberg wrote: I also get this when booting - think it started happening when I started using the new ata-driver. For me it happens when the root is supposed to be mounted (from dmesg): As you can see I am using a seagate disk and I am having the same problem. I've always had this problem with the new ata drivers (on a Western Digital, though). Looks like it's just something we have to Deal With :-( Plus, my CDROM doesn't do audio any more. Tested my CDROM for audio just now - works fine (at least pressing the buttons on the unit, have no softwareplayer to test with so it might not work anyway - my cd is total crap and usually has all kinds of problems..) However, it seems this affects many people using different hardware. The conclusion must be that the ATA drivers needs fixing - not being able to use DMA-mode for disks etc just isn't acceptable, especially considering it worked ok with the wd driver - or did that driver not even try the "better" modes, just falling back to PIO default? I am not familiar with it so I don't know. If it in fact worked before, the ata-guys(Sören, right?) shouldn't have too hard a time getting it to function properly again. Sören, comments? -- Patrik Sundberg - email: [EMAIL PROTECTED] || [EMAIL PROTECTED] --- telefon: 013-178 567 - mobiltelefon: 070-760 22 40 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
