All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Ira Snyder <iws@ovro.caltech.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Simple UART driver help and TTY questions
Date: Tue, 05 Aug 2008 23:21:18 +0200	[thread overview]
Message-ID: <4898C44E.7020303@gmail.com> (raw)
In-Reply-To: <20080805163307.GJ6257@ovro.caltech.edu>

On 08/05/2008 06:33 PM, Ira Snyder wrote:
> Hello LKML,
> So, the problem I have is that when I install this driver, it seems to
> return -EIO before it even hits any of the driver code. I checked this
> by putting a printk at the beginning of every function call in the
> module.
> 
> The error from busybox microcom is this:
> microcom: can't tcsetattr for /dev/ttytiny0: Input/output error
> 
> And cat /dev/ttytiny0:
> cat: /dev/ttytiny0: Input/output error
> 
> Previously to finding this code from LinuxJournal, I had tried to write
> my own skeleton driver, basing it on the drivers/serial/ucc_uart.c code.
> It has the exact same problem. I've attached it as well.
> 
> So, to the best of my research, it seems like the tcsetattr call would
> come in at drivers/char/tty_ioctl.c in tty_mode_ioctl() (the TCSETS
> case). Maybe I'm wrong, though.
> 
> I've built it against both ubuntu's stock kernel (2.6.24 based) and a
> recent pull of the kernel.org kernel.
> 
> I'd really appreciate help figuring out what this problem is.

Attach straces of your tries.

  reply	other threads:[~2008-08-05 21:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 16:33 Simple UART driver help and TTY questions Ira Snyder
2008-08-05 21:21 ` Jiri Slaby [this message]
2008-08-06 19:32   ` Ira Snyder
2008-08-06 21:11 ` Jiri Slaby
2008-08-06 21:46   ` Ira Snyder
2008-08-06 21:51     ` Jiri Slaby

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=4898C44E.7020303@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=iws@ovro.caltech.edu \
    --cc=linux-kernel@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.