Date: Tue, 18 Oct 2005 10:24:49 +0200 From: Psadi <freebsd@psam.se> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: Re: Thoshiba Tecra 8000 with 3com 3CXFE575CT Message-ID: <4354B151.1030100@psam.se> In-Reply-To: <20051017.160614.96601900.imp@bsdimp.com> References: <4353F3D5.6060309@psam.se> <20051017.130631.73017921.imp@bsdimp.com> <43541A46.2050705@psam.se> <20051017.160614.96601900.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh skrev: >In message: <43541A46.2050705@psam.se> > Psadi <freebsd@psam.se> writes: >: M. Warner Losh skrev: >: >: >: When I start it outside and then connect the card it will detect and >: >: configure it correctly. >: > >: >OK. This is a HUGE clue. One that shouldn't be overlooked :-). What >: >it is telling me is that FUNCTION interrupts aren't getting through, >: >but STATUS interrupts ARE getting through. I'll have to go re-read my >: >two TOPIC data sheets to make sure, but I think that the TOPIC chips, >: >especially the older ones, have a number of knobs for function >: >interrupts that are not in the standard bridge chipset. >: > >: >Please refresh my recollection: Did this used to work with 5.4? IIRC, >: >I did some work to fix o2 micro hangs that disabled the function >: >interrupts during card insertion by routing them via IRQ 1 (which the >: >o2micro actually doesn't route, so they just disappear). Maybe that >: >work around had bad effects for the TOPIC95B that you have? >: > >: >Warner >: > >: > >: > >: > >: I have no problem with the network when I run FreeBSD 5.4. I have no >: watchdog timeouts. And I can cvsup the source and ports without any problem. >: >: As a side not ACPI was disable when I tested if it detected the network >: card or not when I inserted it. Though since I didnt notice any diffrent >: when it was on or off I dont think it has any impact. I did do this test >: earlier before you asked but then I just didnt think it was relevant. Of >: this I know it works with ACPI on also since I was running with ACPI >: when I tried it. > >Do you have a second network card, 32- or 16-bits, that you can test >this with also? We need to preclude xl driver bustage in general, or >specific to your submodel as well. > >Warner >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > I have a 3Com Etherlink III wich identifies as ep0 and using that works like a charm :) pccard0: CIS version PCCARD 2.0 or 2.1 pccard0: CIS info: 3Com Corporation, 3C589, TP/BNC LAN Card Ver. 2a, 000002 pccard0: Manufacturer code 0x101, product 0x589 pccard0: function 0: network adapter, ccr addr 10000 mask 3 pccard0: function 0, config table entry 1: I/O card; irq mask ffff; iomask 4, io space 0-f; io8 io16 irqlevel pccard0: function 0, config table entry 3: I/O card; irq mask ffff; iomask 4, io space 0-f; io8 io16 irqlevel ep0: <3Com Corporation 3C589> at port 0x100-0x10f irq 11 function 0 config 1 on pccard0 ep0: bpf attached ep0: Ethernet address: 00:a0:24:ae:be:ad ep0: [MPSAFE] There is no wathcdog timeouts on that card and dl a iso image works fine. Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4354B151.1030100>