linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Otto Moerbeek <otto@cable.a2000.nl>
To: Linux PPC Developer List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: SMP support for Daystar 604e 200MHz dual-processor card >
Date: Wed, 01 Sep 1999 08:18:19 +0200	[thread overview]
Message-ID: <37CCC52B.BBD75BEA@cable.a2000.nl> (raw)


Paul Mackerras write:

> Martin Costabel <costabel@wanadoo.fr> wrote:
> 
> > (On the other hand, I see that Paul M. has CONFIG_SERIAL=m in his
> > standard config files. Does this mean that the serial.c stuff is
> > supposed to work on the PPC?)
> 
> Only with some awful hacks to disable the probing of I/O ports and to
> make it start at ttyS2 instead of ttyS0.  This hack is in my rsync
> trees and in the precompiled kernels I've done.  (I could post a patch
> if necessary.)
> 
> It's not a good long-term solution but I needed something so I could
> use the PC-card modem on my 3400. :-)
> 
> Paul.

I am happy to say that my patches to the standard serial driver which
were developed on LinuxPPC are in the latest 2.3 tree. Apart from making
it run on LinuxPCC, generic support for PCI cards was added, based on
work from various programmers (including myself ;-) )

I have a version of the new serial driver that works on 2.2.10/LinuxPPC
available as standalone module, if anyone is interested.

Otto


-- 
Otto Moerbeek
otto@cable.a2000.nl

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

                 reply	other threads:[~1999-09-01  6:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=37CCC52B.BBD75BEA@cable.a2000.nl \
    --to=otto@cable.a2000.nl \
    --cc=linuxppc-dev@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).