Bug 29866

Summary: Re: NEWCARD support for aironet driver an(4) (kern/24854)
Product: Base System Reporter: Sam Habash <the>
Component: kernAssignee: GNATS administrator <gnats-admin>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 1.0-RELEASE   
Hardware: Any   
OS: Any   

Description Sam Habash 2001-08-19 05:30:00 UTC
 (also getting this into the PR)
 
 On Sat, Aug 18, 2001 at 12:45:03PM -0400, Jonathan Chen wrote:
 > On Sat, Aug 18, 2001 at 09:26:54AM -0700, Sam Habash wrote:
 > > The problem was newcard failing to detect my aironet LMC352.
 > 
 > This is strange... as I understand it, the 350 and 340 are basically the 
 > same programatically...  Without the patch, newcard should be able to 
 > detect the 350 fine when it probes the old-fashioned way, the same way it 
 > detects my 340.  Since oldcard uses the same probe routine, there is no 
 > reason why it should fail when using newcard.  Bleah, it's probably a bug 
 > in newcard.  Perhaps you can do some debugging to find out where exactly it 
 > fails in an_probe()?  Or if it starts working when you change the 
 > DEVMETHOD, perhaps it's an_alloc_irq is failing.  In that case, it would be 
 > nice to find out how exactly it's failing too.
 
 It looks like undoing the patch given in kern/24854 and applying your
 patch instead (and also remembering to uncomment  the line in
 /usr/srs/sys/conf/files referencing 'dev/an/if_an_pccard.c optional an
 pccard') works as well.  I wasn't previously aware of your work, you
 see...
 
 I believe I already tried just uncommenting 'optional ata pccard'
 with the -current source, without any luck. 
 
 > > Looking forward to your patch being committed.  I notice weird behavior 
 > > upon reinsertion currently, it doesn't panic -all- the time. :-)
 > > (looks like the correct URL was http://people.freebsd.org/~jon/newcard.diff.3)
 
 The first time I tried it (not in X) removal and reinsertion of the 
 Aironet card was fine.
 
 The second time (while in X), removal was ok, but card reinsertion caused 
 a reboot (no panic)...
 
 Let me know what you want me to do exactly, in terms of what kind of 
 debugging you need...once I hear back I'll build a debug kernel.
 
 --Sam
Comment 1 dd freebsd_committer freebsd_triage 2001-08-19 22:42:47 UTC
State Changed
From-To: open->closed

not a new pr