Hello from Gregg C Levine usually with Jedi Knight Computers
Go ahead with the bug report, (If that is what PR report means!), if you want
to. However, if your card works with other systems, that definitely do support
NetBSD with out a major hassle, then it should actually be a complaint to Sony,
about their clumsy hardware. (But make that PR directed to the hardware that
caused the major malfunction.) You caught me right, to Sony. Thier designs have
been flaky since the first one wandered off of the assembly line.
----
Gregg C Levine mailto:hansolofalcon@worldnet.att.net
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi (Perhaps the most
powerful of all of the Jedi Knights))
> -----Original Message-----
> From: port-i386-owner@netbsd.org [mailto:port-i386-owner@netbsd.org]On
> Behalf Of Wolfgang Rupprecht
> Sent: Sunday, September 24, 2000 12:31 AM
> To: port-i386@NetBSD.ORG
> Subject: Re: WDC contact needed
>
>
>
> Me:
> > As I mentioned on one of the other lists I just tried to put a CF card
> > socket adaptor and Lexar 8x-speed 16MB CF card for my Sony Vaio 505TX.
>
> My problem seemed to be related to a bios/map setup failure that only
> occurred on my Sony Vaio 505tx.  The exact same Lexar card and
> -current kernel work on:
>
> 	Intel VS440  (venus) + webgear isa/pcmcia adaptor
> 	Toshiba t4800ct (66Mhz 486 dx2)
> 	Sony Vaio 505VE
>
> So I guess I just got really unlucky with my choice of machine.  Every
> other computer works with my 8x Lexar 16MB card.  I do see a gripe
> with something I didn't fully understand:
>
> Sep 22 12:45:23 pasillo /netbsd:                [NG]
> Sep 22 12:45:23 pasillo /netbsd: --------------------------[  1
> devices bogus]
> Sep 22 12:45:23 pasillo /netbsd: WARNING: can't reserve area for I/O APIC.
> Sep 22 12:45:23 pasillo /netbsd:  Physical memory end: 0x03fed000
> Sep 22 12:45:23 pasillo /netbsd:  PCI memory mapped I/O space start:
> 0x04000000
> Sep 22 12:45:23 pasillo /netbsd: [PCIBIOS fixup stage]-----------------------
> Sep 22 12:45:23 pasillo /netbsd:   device vendor product
> Sep 22 12:45:23 pasillo /netbsd:   register space address    size
> Sep 22 12:45:23 pasillo /netbsd: --------------------------------------------
> Sep 22 12:45:23 pasillo /netbsd: 000:00:0 0x8086 0x7100
>
> Is it worth filing a PR for this?  Is this a problem NetBSD should be
> able do deal with or is this just a bad bios address-map setup that
> screws NetBSD?  (That program-loader from Redmond did manage to make
> the lexar work on the effected 505tx, but for all I know it did polled
> I/O).
>
> -wolfgang
> --
>        Wolfgang Rupprecht <wolfgang+gnus@dailyplanet.wsrcc.com>
> 		    http://www.wsrcc.com/wolfgang/
> Coming soon: GPS mapping tools for Open Systems.
> http://www.gnomad-mapping.com/
>