From: Antonio Di Bacco <antonio.dibacco@aruba.it>
To: linuxppc-embedded@ozlabs.org
Subject: Re: HDLC synchronous
Date: Sun, 21 May 2006 20:06:20 +0200 [thread overview]
Message-ID: <200605212006.20178.antonio.dibacco@aruba.it> (raw)
In-Reply-To: <200605211925.49946.antonio.dibacco@aruba.it>
I 've understood well, the hdlc_enet.c driver provided in denk kernel works
if the hdlc controller can use cts and rts but my board has only INPUT,
OUTPUT, CLK_INPUT and CLOCK_OUPUT pins. I imagine this is a synchronous
interface, isn't it?
Bye,
Antonio.
On Sunday 21 May 2006 19:25, Antonio Di Bacco wrote:
> I had a look to hdlc_enet.c in 8xx_io and it seems to me that it only
> supports asynchronous HDLC (speaks about cts rts). Is this true?
>
> Bye,
> Antonio.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next prev parent reply other threads:[~2006-05-21 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 17:25 HDLC synchronous Antonio Di Bacco
2006-05-21 18:06 ` Antonio Di Bacco [this message]
2006-05-21 19:55 ` Wolfgang Denk
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=200605212006.20178.antonio.dibacco@aruba.it \
--to=antonio.dibacco@aruba.it \
--cc=linuxppc-embedded@ozlabs.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