linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Navin Boppuri" <nboppuri@trinetcommunication.com>
To: "Daris Nevil" <dnevil@snmc.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Serial driver help
Date: Tue, 16 Jan 2001 10:21:30 -0000	[thread overview]
Message-ID: <015c01c07fa6$17e3fd10$4a1f76d8@washington> (raw)
In-Reply-To: 3A639801.AFF3DF00@snmc.com


Hello Daris,

Thank you for the link. But all I see there is docs on how to talk to serial
ports. I need some linux data structures info. How is serial.c organized?
How can I port a new uart to serial.c ? etc. etc. Do you know of some place
I can find this?

Thank you,
Navin Boppuri

----- Original Message -----
From: "Daris Nevil" <dnevil@snmc.com>
To: "Navin Boppuri" <nboppuri@trinetcommunication.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Sent: Tuesday, January 16, 2001 12:38 AM
Subject: Re: Serial driver help


> Navin,
>
> Check out http://www.qslinux.org/docs/snmc/serial/index.html, as it may
have
> the info that you need.
>
> Regards,
> Daris Nevil
> SNMC
>
> Navin Boppuri wrote:
>
> > Hello,
> >
> > Can someone tell me where I can find some documentation on how to write
a
> > serial driver in linux using the serial.h and tty data structures? I am
> > using MAX3100 uart connected to the SPI controller. The SPI driver is
fine
> > works just fine. I do see that uart.c is written for uarts connected on
SMC
> > and SCC. All I need to do is to port it for SPI.
> >
> > Thank you,
> > Navin Boppuri
> >
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-01-16 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15 16:46 Serial driver help Navin Boppuri
2001-01-16  0:38 ` Daris Nevil
2001-01-16 10:21   ` Navin Boppuri [this message]
2001-01-16 19:44     ` Daris Nevil

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='015c01c07fa6$17e3fd10$4a1f76d8@washington' \
    --to=nboppuri@trinetcommunication.com \
    --cc=dnevil@snmc.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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).