Re: sio working

1999-11-08 Thread Greg Lehey

On Saturday,  6 November 1999 at 10:49:26 -0700, Warner Losh wrote:
 In message [EMAIL PROTECTED] Greg Lehey writes:
 : Nov  5 17:15:19 mojave /kernel: sio1: configured irq 3 not in bitmap of probed 
irqs 0

 Unless you are running pccardd, you won't see the pccard devices show
 up.  The probe messages that I'm interested in would be the ones that
 say something about it being on pccard0.

 Maybe I'm just confused.

Yes, I think so.  My original message included the probe messages from
pccardd as well.  I commented on sio1 because I had it in the kernel
config file; IIRC this used to be necessary in order for the device to
be found.  I've removed the sio1 definition now (sio0 remains,
corresponding to a hard-wired port on the laptop).  I now get:

   sio0: gdb debugging port
   (hmmm.  I thought I should have got more than that)
   ...
   pccard: card inserted, slot 0
   pccard: card inserted, slot 1
   ep0: 3Com Etherlink III 3C589 at port 0x240-0x24f irq 9 slot 0 on pccard0
   ep0: Ethernet address 00:60:97:40:fb:e1
   sio1 at port 0x2e8-0x2ef irq 5 slot 1 on pccard0
   sio1: type 16550A

I need to check why I'm not getting irq 3 for the port, but everything
else looks OK.

Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sio working

1999-11-08 Thread Warner Losh

In message [EMAIL PROTECTED] Greg Lehey writes:
: I need to check why I'm not getting irq 3 for the port, but everything
: else looks OK.

Likely because you don't have irq 3 listed in the line of available
irqs for pccardd

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sio working

1999-11-07 Thread D. Rock

Warner Losh wrote:
 
 In message [EMAIL PROTECTED] "D. Rock" writes:
 : device  sio0at isa? port IO_COM1 flags 0x10 irq 4
 : device  sio1at isa? port IO_COM2 irq 3
 
 These look good.  IIRC, the kernel I tested with also had:
 
 device  sio2at isa? port IO_COM3 irq 5 disabled
 or
 device  sio2
 
 in it, but I may be misremembering.  Just make sure that you use the
 config entry that gives you a port at 0x3e8, since most laptops have
 COM1 and COM2 which really cannot be disabled (well, the BIOS says you
 can disable them, but I've seen a few where the BIOS disabling is
 broken).
Already did that. I used a config entry for 0x3e8 and one for 0x2e8.
Windows 98 configured the card for IRQ 11 I/O 0x3e8 BTW.

Just some more pccard questions:

When will removing cards (and therefor also suspend/resume) work again?
If I remove the netcard or suspend the machine, the system will freeze.

I also get a NMI if I insert my netcard (DLink DE-660). If DDB is compiled
in I can just continue. Interesting the NMI wasn't generated during initial
configuration (via DHCP), but when I tried some ping tests:

pccard: card inserted, slot 0
sio2: irq maps: 0x105 0x105 0x105 0x105
sio2: probe failed test(s): 0 1 4 6 7 9
sio2: irq maps: 0x105 0x105 0x105 0x105
sio2: probe failed test(s): 0 1 4 6 7 9
pccard: card inserted, slot 1
ed0 at port 0x240-0x25f irq 15 slot 1 on pccard0
ed0: address 00:80:c8:8b:66:e9, type NE2000 (16 bit)
bpf: ed0 attached
NMI ... going to debugger
(
[the first two sio2 lines were with config index for port 0x3e8, the other
ones with config index for 0x2e8]

Daniel


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sio working

1999-11-06 Thread D. Rock

Warner Losh wrote:
 
 In message [EMAIL PROTECTED] "D. Rock" writes:
 : I tried many different combinations. I disabled the onboard serial devices
 : in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with
 : irq 4 but the only thing I get is
 : sio2: configured irq -1071415680 not in bitmap of probed irqs 0
 
 That is very odd...  Do you have sio2 in your config file?  If so just
 take it out and see if that helps or hurts (or replace what is there
 with "devicesio2"  As always when you see odd problems like this,
 try a make clean  make depend  make in the compile directory
 (after reconfiguring).  I don't think it will help the current
 situation, but it won't hurt.
Had tried it all before. No sio2 in kernel. Below is the complete config file

Daniel


---
machine i386

ident   LAPTOP

maxusers6

options PQ_LARGECACHE

cpu I686_CPU

options COMPAT_43
#optionsUSER_LDT
options SYSVSHM
options SYSVSEM
options SYSVMSG
options MD5
#optionsDDB
#optionsDDB_UNATTENDED
options KTRACE
options PERFMON
options UCONSOLE
#optionsUSERCONFIG
#optionsVISUAL_USERCONFIG
options INET

pseudo-device   ether
#pseudo-device  sppp
pseudo-device   loop
pseudo-device   bpf
pseudo-device   tun

#optionsMROUTING
#optionsIPFIREWALL
#optionsIPFIREWALL_VERBOSE
#optionsIPFIREWALL_FORWARD
#optionsIPFIREWALL_DEFAULT_TO_ACCEPT
#optionsIPDIVERT
#optionsIPSTEALTH

options ICMP_BANDLIM

#optionsDUMMYNET

options FFS
options NFS

options NFS_NOSERVER
options CD9660
options MSDOSFS
options PROCFS
options FFS_ROOT

options SOFTUPDATES

options QUOTA

options P1003_1B
options _KPOSIX_PRIORITY_SCHEDULING
options _KPOSIX_VERSION=199309L

#controller scbus0
#device ch0
#device da0
#device sa0
#device cd0
#device pass0
#optionsSCSI_REPORT_GEOMETRY

pseudo-device   pty
#pseudo-device  speaker
#pseudo-device  gzip
#pseudo-device  vn
#pseudo-device  snp 3

options MSGBUF_SIZE=20480

controller  isa0
#optionsAUTO_EOI_1

#controller pnp0
controller  atkbdc0 at isa? port IO_KBD
device  atkbd0  at atkbdc? irq 1
options ATKBD_DFLT_KEYMAP
makeoptions ATKBD_DFLT_KEYMAP="german.iso"

device  psm0at atkbdc? irq 12
#optionsPSM_HOOKAPM
#optionsPSM_RESETAFTERSUSPEND

device  vga0at isa? port ? conflicts
options VGA_WIDTH90
options VESA
pseudo-device   splash

device  sc0 at isa?
options MAXCONS=6
options SC_DFLT_FONT
makeoptions SC_DFLT_FONT=iso
options SC_PIXEL_MODE

device  npx0at nexus? port IO_NPX flags 0x0 irq 13

#controller ata0
#device atadisk0
#device atapicd0

controller  wdc0at isa? port IO_WD1 flags 0xe0ffc0ff irq 14
device  wd0 at wdc0 drive 0
options IDE_DELAY=2000
device  wcd0

controller  fdc0at isa? port IO_FD1 irq 6 drq 2
device  fd0 at fdc0 drive 0

device  sio0at isa? port IO_COM1 flags 0x10 irq 4
device  sio1at isa? port IO_COM2 irq 3
#optionsEXTRA_SIO=1

device  ed0
#device xe0

#controller snd0
#device sb0 at isa? port 0x220 irq 5 drq 1
#device sbxvi0  at isa? port 0x220 irq 5 drq 5 conflicts
#device sbmidi0 at isa? port 0x330
#device opl0at isa? port 0x388
#device mpu0at isa? port 0x330

device  pcm0at isa? port 0x220 irq 5 drq 1 flags 0x15

#device pca0at isa? port IO_TIMER1

device  apm0at nexus?
device  joy0at isa? port IO_GAME

#controller miibus0

controller  pci0

controller  card0
controller  pcic0   at isa? irq 10
controller  pcic1   at isa? irq 10
#options PCIC_RESUME_RESET

#controller smbus0
#controller intpm0

#device smb0at smbus?

#controller iicbus0
#controller iicbb0

#device ic0 at iicbus?
#device iic0at iicbus?
#device iicsmb0 at iicbus?

#options AVM_A1_PCMCIA
#device isic0

#pseudo-device  "i4bq921"
#pseudo-device  "i4bq931"
#pseudo-device  "i4b"
#pseudo-device   "i4btrc"   4
#pseudo-device   "i4bctl"
#pseudo-device   "i4brbch"   4
#pseudo-device   "i4btel"2
#pseudo-device   "i4bipr"   4
#optionsIPR_VJ
#pseudo-device  "i4bisppp"  4

controller  ppbus0
#controller vpo0at ppbus?
device  lpt0at ppbus?
device  ppi0at ppbus?

device  ppc0at isa? port? irq 7 drq 3

controller  uhci0
controller  usb0
device  ugen0
#device uhid0
#device ukbd0
#device ulpt0
#controller umass0
#device 

Re: sio working

1999-11-06 Thread D. Rock

Warner Losh wrote:
 
 In message [EMAIL PROTECTED] "D. Rock" writes:
 : I tried many different combinations. I disabled the onboard serial devices
 : in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with
 : irq 4 but the only thing I get is
 : sio2: configured irq -1071415680 not in bitmap of probed irqs 0
 
 That is very odd...  Do you have sio2 in your config file?  If so just
 take it out and see if that helps or hurts (or replace what is there
 with "devicesio2"  As always when you see odd problems like this,
 try a make clean  make depend  make in the compile directory
 (after reconfiguring).  I don't think it will help the current
 situation, but it won't hurt.
With the latest -current I get a slightly different output:

Nov  7 03:34:47  /kernel.new: pccard: card inserted, slot 0
Nov  7 03:34:57  /kernel.new: sio2: irq maps: 0x105 0x105 0x105 0x105
Nov  7 03:34:57  /kernel.new: sio2: probe failed test(s): 0 1 4 6 7 9
Nov  7 03:34:57  pccardd[15]: driver allocation failed for Intelligent(PCMCIA 
FAX+MODEM): Device not configured


How intelligent is pccardd? This card has several config entries, but only the
first one contains also possible IRQs, the additional entries only contain
I/O ports. So I also tried to use the first one (and disabling the conflicting
sio0 in BIOS + kernel config)


Daniel


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sio working

1999-11-06 Thread Warner Losh

In message [EMAIL PROTECTED] "D. Rock" writes:
: With the latest -current I get a slightly different output:
: 
: Nov  7 03:34:47  /kernel.new: pccard: card inserted, slot 0
: Nov  7 03:34:57  /kernel.new: sio2: irq maps: 0x105 0x105 0x105 0x105
: Nov  7 03:34:57  /kernel.new: sio2: probe failed test(s): 0 1 4 6 7 9
: Nov  7 03:34:57  pccardd[15]: driver allocation failed for Intelligent(PCMCIA 
:FAX+MODEM): Device not configured

OK, looks like it failed to probe.  At a guess is appears that this
card is conflicting with something else, otherwise it wouldn't be
failing these probes.

: How intelligent is pccardd? This card has several config entries,
: but only the first one contains also possible IRQs, the additional
: entries only contain I/O ports. So I also tried to use the first one
: (and disabling the conflicting sio0 in BIOS + kernel config)

pccardd does what you tell it to do.  The IRQs in the CIS entries are
just hints anyway, pccardd is free to ignore them if it sees fit.
They are there to tell the BIOS that "cards of this type are generally
mapped to these IRQs, be nice to stupid drivers and map them there
please."  FreeBSD doesn't have any stupid drivers. :-)

However, I don't think the irq issue is your problem.  I think that it
may be that you are trying to map a serial port to where one might
already exist.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sio working

1999-11-06 Thread Warner Losh

In message [EMAIL PROTECTED] "D. Rock" writes:
: device  sio0at isa? port IO_COM1 flags 0x10 irq 4
: device  sio1at isa? port IO_COM2 irq 3

These look good.  IIRC, the kernel I tested with also had:

device  sio2at isa? port IO_COM3 irq 5 disabled
or
device  sio2

in it, but I may be misremembering.  Just make sure that you use the
config entry that gives you a port at 0x3e8, since most laptops have
COM1 and COM2 which really cannot be disabled (well, the BIOS says you
can disable them, but I've seen a few where the BIOS disabling is
broken).

: #optionsEXTRA_SIO=1

This is totally bogus and should never ever be used.  Better to remove
it completely from your config file, lest the temptation is there to
use it.

: options HZ=500

I don't think this option will work, but I don't think that's what is
breaking things.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



RE: sio working

1999-10-23 Thread Will Andrews

On 23-Oct-99 Warner Losh wrote:
 OK.  I managed to get sio and ep working on the plane back from
 FreeBSDCon'99.  There are some problems with card eject at the moment,
 but will be committing things to the tree shortly.

I will be your guinea pig, if you like. :-)

--
Will Andrews [EMAIL PROTECTED]
GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ 
G+ e- h! r--+++ y?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sio working

1999-10-23 Thread Warner Losh

In message [EMAIL PROTECTED] Will Andrews writes:
: I will be your guinea pig, if you like. :-)

Grab the current patches from
http://www.freebsd.org/~imp/pccard-snap.patch
but read my other posting about the warnings and such.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sio working

1999-10-23 Thread Will Andrews

On 23-Oct-99 Warner Losh wrote:
 In message [EMAIL PROTECTED] Will Andrews
 writes:
: I will be your guinea pig, if you like. :-)
 
 Grab the current patches from
   http://www.freebsd.org/~imp/pccard-snap.patch
 but read my other posting about the warnings and such.

As of yet, I haven't tested your code. I will be, in a few. I took the
opportunity to go over the patch first.

I noticed a little discrepancy in ep_pccard_identify, where the switch() does
not offer a default: case. You should put something like that in there and call
the card "Unknown 3Com card" or somesuch. Same for ep_pccard_card_attach().

That's all I can manage from a quick skim of your code.

Well, I'm gonna test out this kernel patch. (after safely backing up sys/).


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sio working

1999-01-04 Thread Warner Losh

In message [EMAIL PROTECTED] Greg Lehey writes:
: Nov  5 17:15:19 mojave /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0

Unless you are running pccardd, you won't see the pccard devices show
up.  The probe messages that I'm interested in would be the ones that
say something about it being on pccard0.

Maybe I'm just confused.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sio working

1999-01-04 Thread Warner Losh

In message [EMAIL PROTECTED] "D. Rock" writes:
: I tried many different combinations. I disabled the onboard serial devices
: in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with
: irq 4 but the only thing I get is
: sio2: configured irq -1071415680 not in bitmap of probed irqs 0

That is very odd...  Do you have sio2 in your config file?  If so just
take it out and see if that helps or hurts (or replace what is there
with "devicesio2"  As always when you see odd problems like this,
try a make clean  make depend  make in the compile directory
(after reconfiguring).  I don't think it will help the current
situation, but it won't hurt.

Warner




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sio working

1999-01-03 Thread Greg Lehey

On Friday,  5 November 1999 at 23:02:52 +0100, D. Rock wrote:
 Warner Losh wrote:

 OK.  I managed to get sio and ep working on the plane back from
 FreeBSDCon'99.  There are some problems with card eject at the moment,
 but will be committing things to the tree shortly.

 Basically, I completely gutted the compatibilty layer and it became
 much easier.  More later after I've had a chance to spend time with my
 wife and unwind from the drive back.

 I didn't have any luck using the sio driver with my card.

 Card info from "pccardc dumpcis":
 snip

 card "Intelligent" "PCMCIA FAX+MODEM"
 #   config 0x0f "sio2" ?
 #   config 0x17 "sio2" ?
 config 0x1f "sio2" ?
 #   config 0x27 "sio2" ?

On my Dell Latitude CPi I have:

device  sio0at isa? port IO_COM1 flags 0x90 irq 4
device  sio1at isa? port IO_COM2 irq 3

sio0 really exists; it seems that sio1 shouldn't be there, since I get
the message

Nov  5 17:15:39 mojave /kernel: devclass_alloc_unit: sio1 already exists, using next 
available unit number
Nov  5 17:15:39 mojave /kernel: sio2 at port 0x2e8-0x2ef irq 5 slot 1 on pccard0
Nov  5 17:15:39 mojave /kernel: sio2: type 16550A

Anyway, this configuration works: at least I can use it to dial in to
a remote system.

 I tried many different combinations. I disabled the onboard serial devices
 in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with
 irq 4 but the only thing I get is
 sio2: configured irq -1071415680 not in bitmap of probed irqs 0

 The irq number isn't always the same. It seems to be a pointer.

Or junk.

 Here the remaining relevant lines from my configuration:
 controller  card0
 controller  pcic0   at isa? irq 10
 controller  pcic1   at isa? irq 10

ISTR you should put card0 after pcic0 and pcic1.  Also, I have no
interrupts:

device  pcic0   at isa?
device  pcic1   at isa?
controller  card0

 Boot output:
 pcic-pci0: TI PCI-1131 PCI-CardBus Bridge at device 10.0 on pci0
 pcic-pci1: TI PCI-1131 PCI-CardBus Bridge at device 10.1 on pci0
 [...]
 pcic0: VLSI 82C146 at irq 10 on isa0
 pccard0: PC Card bus -- kludge version on pcic0
 pccard1: PC Card bus -- kludge version on pcic0

I have:
Nov  5 17:15:19 mojave /kernel: pcic-pci0: TI PCI-1131 PCI-CardBus Bridge irq 11 at 
device 3.0 on pci0
Nov  5 17:15:19 mojave /kernel: pcic-pci1: TI PCI-1131 PCI-CardBus Bridge irq 11 at 
device 3.1 on pci0
...
Nov  5 17:15:19 mojave /kernel: pcic0: VLSI 82C146 on isa0
Nov  5 17:15:19 mojave /kernel: pccard0: PC Card bus -- kludge version on pcic0
Nov  5 17:15:19 mojave /kernel: pccard1: PC Card bus -- kludge version on pcic0
Nov  5 17:15:19 mojave /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0
Nov  5 17:15:19 mojave /kernel: sio0: type 16550A
Nov  5 17:15:19 mojave /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0

Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message