linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: <rmcguire@videopresence.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Driver - HDLC 83xx QUICC Engine??
Date: Wed, 16 Jan 2008 01:34:51 +0100	[thread overview]
Message-ID: <000301c857d7$9c1eaba0$d45c02e0$@tjernlund@transmode.se> (raw)
In-Reply-To: <000301c857d7$0195f890$6405a8c0@absolut>

> -----Ursprungligt meddelande-----
> Fr=E5n: Russell McGuire [mailto:rmcguire@videopresence.com]
> Skickat: den 16 januari 2008 01:31
> Till: 'Joakim Tjernlund'
> Kopia: linuxppc-embedded@ozlabs.org
> =C4mne: RE: Driver - HDLC 83xx QUICC Engine??
>=20
> Jocke,
>=20
> I'll let you know if I find any.  For a starting point, I have an QE =
ATM
> driver, that is more than likely similar in design <though no Ethernet
> interface>, as it supports the QE engine, and just turns the UCC into =
ATM
> mode, as opposed to HDLC mode. Would imagine the buffering, IO, =
interrupts
> are similar. I am still in process of porting it up from the 82xx CPU.
>=20
> Although HDLC how it registers itself into the kernel is a mystery to =
me, I
> am having trouble finding any HDLC drivers to model this after.  Know =
of any
> specs? API? Etc...

Sorry but I don't know. Luckily for me I don't have too either.

 Jocke

  reply	other threads:[~2008-01-16  0:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1200358805.3196.linuxppc-embedded@ozlabs.org>
2008-01-15 19:51 ` Driver - HDLC 83xx QUICC Engine?? Russell McGuire
2008-01-16  0:18   ` SV: " Joakim Tjernlund
2008-01-16  0:30     ` Russell McGuire
2008-01-16  0:34       ` Joakim Tjernlund [this message]
2008-01-17 22:11     ` Russell McGuire
2008-01-17 23:53       ` Joakim Tjernlund

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='000301c857d7$9c1eaba0$d45c02e0$@tjernlund@transmode.se' \
    --to=joakim.tjernlund@transmode.se \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rmcguire@videopresence.com \
    /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).