From: Daris A Nevil <dnevil@snmc.com>
To: clark@esteem.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Talking to the parrallel i/o ports
Date: Tue, 24 Oct 2000 15:04:58 -0500 [thread overview]
Message-ID: <39F5EB6A.FFC195FA@snmc.com> (raw)
In-Reply-To: 5.0.0.25.1.20001024094825.00a47240@pop.esteem.com
Conn,
Sorry for the confusion. You will need to download the tarball for the
qslinux source, expand that out, and then look in the directories
snmc/qslinux/kernel and snmc/qspin.
You can download the latest kernel tarball from:
ftp://qslinux.org/pub/qslinux/
Regards,
Daris
clark@esteem.com wrote:
>
> Hi Daris,
>
> I'm having a little trouble locating the source you were talking
> about. I have tried looking at http://qslinux.org/snmc/qslinux/kernel and
> http://qslinux.org/snmc/qspin but they come up as 404 Not Found. I have
> also looked at your ftp site under ftp://qslinux.org/snmc/qslinux/kernel
> and ftp://qslinux.org/snmc/qspin with no luck. I was able to find
> ftp://qslinux.org/pub/qslinux/ with complete source tar files. Do I have to
> down load one of these?
>
> Thanks for the help.
>
> Conn
>
> At 05:27 PM 10/23/00 -0500, you wrote:
> >Hello Conn,
> >
> >I wrote a nice little I/O control subsystem for the MPC850. It is in
> >QSLinux (http://qslinux.org, ftp::/qslinux.org), and is in the
> >subdirectories snmc/qslinux/kernel and snmc/qspin.
> >
> >The subsystem gives you the ability to check, request, and configure the
> >function of the I/O pins on the MPC850. It is modeled after the I/O
> >address allocator for the 80x86 architecture. You can access the
> >subsystem either from kernel space, or from a user space program.
> >
> >You will need to modify the subsystem for operation with other MPC8xx
> >processor (i.e. the MPC860 has more I/O pins). But this should not be
> >difficult.
> >
> >I don't have a command-line driven program that interfaces to the
> >subsystem, but if you write one and are willing to share it I would love
> >to have a copy :-).
> >
> >Regards,
> >Daris
> >
> >
> >clark@esteem.com wrote:
> > >
> > > Hello everyone,
> > > my stuff blah blah blah
> > >
> >
> >--
> >Daris A Nevil
> >Simple Network Magic Corporation
> >401 Kentucky Lane
> >McKinney, TX 75069
> >214-793-7757
> >dnevil@snmc.com
> >www.snmc.com
> >quickstack.com
> >qslinux.org
>
> *****************************************************************
> If you live at home long enough, your parrents will move out.
> *****************************************************************
>
> Conn Clark
> Engineering Stooge clark@esteem.com
> Electronic Systems Technology Inc. www.esteem.com
>
> Stock Ticker Symbol ELST
>
--
Daris A Nevil
Simple Network Magic Corporation
401 Kentucky Lane
McKinney, TX 75069
214-793-7757
dnevil@snmc.com
www.snmc.com
quickstack.com
qslinux.org
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-24 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 16:51 Talking to the parrallel i/o ports clark
2000-10-24 20:04 ` Daris A Nevil [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-23 21:44 clark
2000-10-23 22:27 ` Daris A 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=39F5EB6A.FFC195FA@snmc.com \
--to=dnevil@snmc.com \
--cc=clark@esteem.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).