linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Kawa <jfk@zeus.polsl.gliwice.pl>
To: Steve Youngs <sryoungs@bigpond.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test11 -- Failed to open /dev/ttyS0: No such device
Date: Sun, 30 Nov 2003 23:22:22 +0100	[thread overview]
Message-ID: <20031130222222.GA11809@finwe.eu.org> (raw)
In-Reply-To: <microsoft-free.87ekvpc0ms.fsf@eicq.dnsalias.org>

Steve Youngs wrote:

>   JK> bert hubert wrote:
>   >>> Does anyone have modem working in 2.6.0-test11?
>   >>> I have external modem connected to /dev/ttyS0 (COM1).  Kernel
>   >>> 2.6.0-test11 give me

>   JK> It reminds me, that I had to add serial to the list of modules
>   JK> loading at start to get back access to /dev/ttyS* 
>   JK> (while upgrading from -test9 to -test10). 

> I _think_ this patch will bring back auto-loading of the serial module
> for you.  Please let me know how it goes. 

Well: patched, installed new serial_core.ko, then depmod -a, and try to
access ttySwhatever.

I don't see any difference... If I understood correctly, it could not load 
my 'fake' serial module anyway (?)

BTW. only changes,I think could affect serial directly and
     made betwen test9 and test10 are:

diff -Nru a/drivers/serial/serial_core.c b/drivers/serial/serial_core.c
--- a/drivers/serial/serial_core.c	Sun Nov 23 17:33:38 2003
+++ b/drivers/serial/serial_core.c	Sun Nov 23 17:33:38 2003
@@ -1707,6 +1707,9 @@
 		strcat(stat_buf, "\n");
 	
 		ret += sprintf(buf + ret, stat_buf);
+	} else {
+		strcat(buf, "\n");
+		ret++;
 	}
 #undef STATBIT
 #undef INFOBIT

diff -Nru a/include/linux/serial.h b/include/linux/serial.h
--- a/include/linux/serial.h	Sun Nov 23 17:33:38 2003
+++ b/include/linux/serial.h	Sun Nov 23 17:33:38 2003
@@ -49,7 +49,6 @@
 	unsigned short	iomem_reg_shift;
 	unsigned int	port_high;
 	unsigned long	iomap_base;	/* cookie passed into ioremap */
-	int	reserved[1];
 };
 
 /*

I could try to narrow it down to some -bk, but it will take time...

PS. I wonder - could it be, that somewhere in the middle of 
    decision process test9 > test10 (as test1something)

bye

-- 
Jacek Kawa  **Oh, Lord, bless this thy hand grenade that with it thou
              mayest blow thy enemies to tiny bits, in thy mercy.**

  parent reply	other threads:[~2003-11-30 22:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30  7:17 2.6.0-test11 -- Failed to open /dev/ttyS0: No such device William Park
2003-11-30 10:23 ` bert hubert
2003-11-30 11:36   ` Jacek Kawa
2003-11-30 15:54     ` Steve Youngs
2003-11-30 16:00       ` Russell King
2003-11-30 22:22       ` Jacek Kawa [this message]
2003-12-01  2:17         ` Steve Youngs
2003-12-01  7:28           ` Jacek Kawa
2003-11-30 19:05     ` William Park
2003-11-30 18:40   ` William Park

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=20031130222222.GA11809@finwe.eu.org \
    --to=jfk@zeus.polsl.gliwice.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sryoungs@bigpond.net.au \
    /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).