From owner-freebsd-mobile Thu Feb 10 23:45:37 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by builder.freebsd.org (Postfix) with ESMTP id 5B01B469B for ; Thu, 10 Feb 2000 23:45:30 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA49450; Fri, 11 Feb 2000 00:45:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA48200; Fri, 11 Feb 2000 00:46:09 -0700 (MST) Message-Id: <200002110746.AAA48200@harmony.village.org> To: Soren Schmidt Subject: Re: Update to pccard ata changes (removal support) Cc: ambrisko@whistle.com (Doug Ambrisko), freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 11 Feb 2000 08:34:51 +0100." <200002110734.IAA41570@freebsd.dk> References: <200002110734.IAA41570@freebsd.dk> Date: Fri, 11 Feb 2000 00:46:09 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200002110734.IAA41570@freebsd.dk> Soren Schmidt writes: : It seems Warner Losh wrote: : > This patch works OK for me. My CF card works w/o a hitch. My cdrom : > doesn't work, my guess is some kind of powerup sequence for the cdrom : > is needed before it will detect: : : How are they located the CF on ata1 and the CDROM on ata2 ?? cdrom at ata1, eject cdrom at ata2. I then rebooted and the CF worked w/o incident (I didn't try before the reboot). Sorry I wasn't clear. : > ata1: iobase=0x0170 altiobase=0x0178 bmaddr=0x0000 : > ata1: mask=03 status0=00 status1=00 : > ata1: mask=03 status0=00 status1=00 : > ata1: devices = 0x0 : > ata2: iobase=0x0240 altiobase=0x0248 bmaddr=0x0000 : > ata2: mask=03 status0=50 status1=00 : > ata2: mask=03 status0=50 status1=00 : > ata2: devices = 0x1 : > : > My CLIK panics my kernel: : > : > ata1 at port 0x180-0x18f irq 11 slot 0 on pccard0 : > ata2-master: floppy device - NO DRIVER! : > Fatal trap 12: page fault while in kernel mode : : Damn I thought I fixed that panic, is this with the latest -current ?? : Ouch I see it, commit comming.... Yes. Here's more details, lemme know if you need more. Looks like the floppy driver needs a little work. Or it might just be the two windows problem. What's in the altstatus register? What is it used for? pccard: card inserted, slot 0 ata1 at port 0x180-0x18f irq 11 slot 0 on pccard0 (null): MODE_SENSE_BIG - ILLEGAL REQUEST asc=24 ascq=00 error=00 (null): MODE_SENSE_BIG - ILLEGAL REQUEST asc=24 ascq=00 error=00 (null): MODE_SENSE_BIG - ILLEGAL REQUEST asc=24 ascq=00 error=00 ata2-master: floppy device - NO DRIVER! Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0221ca9 stack pointer = 0x10:0xc86b8cd4 frame pointer = 0x10:0xc86b8d04 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 50 (pccardd) interrupt mask = none : > Also, the altiobase is wrong for the cdrom. It should be the usual : > isa ata addresses. : : Uhm, if it bound via the pccard routines it can not be at the usual : place, there is no way to know when it should be one or the other... Yes. That was a comment about the pccard attachment code not being completely right. Sorry I wasn't clear. I know how to tell the difference and hope to make a small change shortly. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message