mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Shawn Starr <shawn.starr@datawire.net>
Cc: lkm <linux-kernel@vger.kernel.org>
Subject: Re: HPNA 2.0 Information that might be helpful
Date: Wed, 26 Sep 2001 11:15:30 +0300	[thread overview]
Message-ID: <20010926111530.G11046@mea-ext.zmailer.org> (raw)
In-Reply-To: <3BB1485A.F964EF93@datawire.net>
In-Reply-To: <3BB1485A.F964EF93@datawire.net>; from shawn.starr@datawire.net on Tue, Sep 25, 2001 at 11:15:38PM -0400

On Tue, Sep 25, 2001 at 11:15:38PM -0400, Shawn Starr wrote:
> http://www.homepna.org/docs/paper500.pdf
> I found this document via google and it tells you the format for an
> HPNA 2.0 frame
>   Shawn.

The HPNA looks, for all intents and purposes, as Ethernet.
The interesting question will be card drivers.

If card vendor writes a driver themselves, and sends it out
in source, we are happy.   If they give (to selected few
contact people) sufficient information for writing a driver,
that works too.

Reading the Broadcom  BCM4211 and BCM4413 product briefs
does give me an idea that the thing wont be quite simple.
That is, unless the Soft-V.90 is ditched.
(Biggest code is at that modem stuff anyway.)

Even writing a soft-modem into separate user-space entity
with only the low-level hardware driving in the kernel
is doable by letting the modem stuff to be binary-only.
For several reasons that is most likely appropriate way
even to do it.  Soft-modem has no place in kernel.

/Matti Aarnio

  reply	other threads:[~2001-09-26  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26  3:15 Shawn Starr
2001-09-26  8:15 ` Matti Aarnio [this message]
2001-09-27 23:45 ` HPNA 2.0 Update Binary only driver released as beta Shawn Starr

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=20010926111530.G11046@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn.starr@datawire.net \
    /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

all inboxes | Powered by JetHome®