linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Michalkiewicz <marekm@amelek.gda.pl>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Marek Michalkiewicz <marekm@amelek.gda.pl>,
	twaugh@redhat.com, serial24@macrolink.com,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] fix parport_serial / serial link order (for 2.4.20-pre8)
Date: Mon, 30 Sep 2002 12:27:09 +0200 (CEST)	[thread overview]
Message-ID: <E17vxld-0004kB-00@alf.amelek.gda.pl> (raw)
In-Reply-To: <Pine.LNX.4.44.0209300515420.24805-100000@montezuma.mastecende.com>

> Tim would know better there since he removed it, but iirc it had something 
> to do with the BARs used, hmm your card has the same PCI id and is serial 
> neutered to an extent, what happens if you treat it as if it really does 
> have both serial ports there? Does it still work without causing other 
> problems so you can safely ignore it? FYI, Interrupt driven works great 
> for me.

Hmm, not sure what you're talking about - I have both serial ports working
fine, sharing one IRQ.  Not sure what the regions 3-5 are for though...
If you have a parport IRQ sharing patch to test, you can send it to me.

The card is just a bare NM9835 chip + two GD75232 chips (RS232 drivers),
no configuration EEPROM mounted, so all data is from the NM9835 defaults
and all such cards should work the same way...

00:09.0 Communication controller: Unknown device 9710:9835 (rev 01)
	Subsystem: LSI Logic / Symbios Logic (formerly NCR): Unknown device 0012
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 9
	Region 0: I/O ports at ac00 [size=8]
	Region 1: I/O ports at b000 [size=8]
	Region 2: I/O ports at b400 [size=8]
	Region 3: I/O ports at b800 [size=8]
	Region 4: I/O ports at bc00 [size=8]
	Region 5: I/O ports at c000 [size=16]

parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
parport_pc: Via 686A parallel port: io=0x378
...
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
PCI parallel port detected: 9710:9835, I/O at 0xb400(0x0)
parport1: PC-style at 0xb400 [PCSPP,TRISTATE,EPP]
ttyS04 at port 0xac00 (irq = 9) is a 16550A
ttyS05 at port 0xb000 (irq = 9) is a 16550A
lp0: using parport0 (polling).
lp0: console ready
lp1: using parport1 (polling).

> link order shouldn't affect the decision seeing as it affects all 
> parport_serial anyway. You might have to wait it out and see what Tim/Ed 
> have to say but i do have patches for both lying about.

OK, I'll try to be patient ;)

Marek


  reply	other threads:[~2002-09-30 10:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-26 20:05 [patch] fix parport_serial / serial link order (for 2.4.20-pre8) Marek Michalkiewicz
2002-09-27  1:18 ` Zwane Mwaikambo
2002-09-27  6:35   ` Marek Michalkiewicz
2002-09-28  4:24     ` Zwane Mwaikambo
2002-09-29 18:00       ` Marek Michalkiewicz
2002-09-29 19:14         ` Zwane Mwaikambo
2002-09-29 20:24           ` Marek Michalkiewicz
2002-09-30  9:20             ` Zwane Mwaikambo
2002-09-30 10:27               ` Marek Michalkiewicz [this message]
2002-09-30  9:40 ` Tim Waugh
2002-09-30  9:49   ` Russell King
2002-09-30 10:07   ` Marek Michalkiewicz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E17vxld-0004kB-00@alf.amelek.gda.pl \
    --to=marekm@amelek.gda.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serial24@macrolink.com \
    --cc=twaugh@redhat.com \
    --cc=zwane@linuxpower.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).