From: RChan <rspchan@starhub.net.sg>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sunsu.c
Date: Thu, 21 Oct 2004 08:30:37 +0000 [thread overview]
Message-ID: <417773AD.2070309@starhub.net.sg> (raw)
In-Reply-To: <4175D5D4.3090702@starhub.net.sg>
Here's a fix-up earlier in the code path so that the irq is not reported
as 0;
this occurs in sunsu_serial_init (actually that makes more sense) then where
I originally put it in sunsu_startup.
I now get
ttyS0 at MMIO 0x7fe010003f8 (irq = 7607552) is a 16550A
ttyS1 at MMIO 0x7fe010002e8 (irq = 7607552) is a 16550A
serial_core.c obviously isn't going to use __irq_itoa() to get a "nice"
representation
of the irq so these irq numbers look weird but more reassuring than 0.
--- /usr/src/linux.old/drivers/serial/sunsu.c.ORIG 2004-10-20
10:03:52.000000000 +0800
+++ /usr/src/linux/drivers/serial/sunsu.c 2004-10-20
18:14:23.000000000 +0800
@@ -1092,6 +1092,7 @@
up->port.membase = (char *)
isa_dev->resource.start;
up->port.mapbase = isa_dev->resource.start;
up->irq = isa_dev->irq;
+ up->port.irq = up->irq;
goto ebus_done;
}
}
David S. Miller wrote:
>On Wed, 20 Oct 2004 11:04:52 +0800
>RChan <rspchan@starhub.net.sg> wrote:
>
>
>
>>The following patch fixes an oops in the serial subsystem
>>when using a agetty/login on ttyS[01] reported by me on the
>>mailing list. I suspect member values from the uart_sunsu_port structure are
>>not correctly transferred to the uart_port structure?
>>
>>
>
>Thanks a lot, I'll take a closer look at your bug fix
>soon. I think the propagation should be occuring
>automatically and I want to find out why that might
>not be occuring.
>
>
>
next prev parent reply other threads:[~2004-10-21 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 3:04 [PATCH] sunsu.c RChan
2004-10-21 5:19 ` David S. Miller
2004-10-21 8:30 ` RChan [this message]
2004-10-31 21:45 ` David S. Miller
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=417773AD.2070309@starhub.net.sg \
--to=rspchan@starhub.net.sg \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.