From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Steve Boley <steve@nams.net>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Old Driver Code Using Streams
Date: Sun, 19 Jul 2020 01:01:26 -0400 [thread overview]
Message-ID: <177747.1595134886@turing-police> (raw)
In-Reply-To: <CA+Xm7BTt5KKGimZqGYBngfZuT+VxCsqgG4m01rGocyEGFt3WUg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1031 bytes --]
On Wed, 15 Jul 2020 15:44:33 -0500, Steve Boley said:
> I have old source for a proprietary card that used to dev for both unix and
> linux and uses the old sysV streams code for talking to the native
> operating system. The streams is long out of development and trying to port
> it to working CentOS 6 2.6.32 is proving less than fun.
If 2.6.32 is proving hard, getting to a *modern* release will be even worse...
> I'd like to know what we need to use within the native linux kernel to
> ditch the streams package altogether and just rewrite both ends.
Well... let's make the assumption that the streams stuff was the result of
really good pharmaceuticals.
What sort of card is it? Is there anything *remotely* similar already in-tree?
Even if this card can't leverage any driver directly, even just knowing "Oh, it's
a networking card, so our driver should look like other networking card drivers"
or "It's an accelerometer, so let's do it the same way as the last one that went
into the kernel" is a huge step forward.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-07-19 5:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 20:44 Old Driver Code Using Streams Steve Boley
2020-07-19 5:01 ` Valdis Klētnieks [this message]
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=177747.1595134886@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=steve@nams.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;
as well as URLs for NNTP newsgroup(s).