Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Thomas Marteau <marteaut@esiee.fr>
To: "M. Grabert" <xam@deathsdoor.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Generic Parisc Linux Kernel Questions & 9000/730 success report
Date: Tue, 06 Feb 2001 23:12:40 +0100	[thread overview]
Message-ID: <3A8076D8.CF5E8CCD@esiee.fr> (raw)
In-Reply-To: Pine.LNX.4.21.0102061808500.2465-100000@sgate.charlysworld.de

Hi Max,

	Here is the ESIEE Team answer! (Exactly what our experince told us :))
smb is one of the most famous questions of LWE Paris. So someone will
have to port it.
We do not think that it has been done yet

> smb won't compile
do not know> netware won't compile
do not know> ppp_sync won't compile

> fbcon-sti won't compile (at least when I don't compile STI-console)
The matter of frame buffer is quite complex. When we look at the code,
the fb-sti init is the first then came up the sti-console init. This
explained the snow you have on the screeen when you compile a kernel
with fbcon-sti and sti-console. This info can be out of date! If someone
has a better news , speak :)

> hwclock doesn't work (can't use /dev/rtc), 'though I seems the
>    time and date is read correctly (but hwclock can't set them).
>    Is this a known problem ?
We think also about /dev/rtc as Grant told you

> Is the well known problem of the missing termcap fixed in the new nfsroot?
Do not think so
> 
> Is is enough to copy nfsroot onto the scsi disc and adopt /etc/fstab,
>    or should I use base.tgz ? what's the difference ?
As we use the network for nfs and ftp, you have to configure the
following files:
/etc/hostname
/etc/network/interfaces
/etc/fstab
also you have to check
/dev/console for sti it should be linked to /dev/tty0
	     for serial it should be linked to /dev/ttyS0
It seems interesting to lokk into /etc/inittab 

> Mhhh. missing ftp and (open)ssh, strace in (old) nfstools. Are they in the
>    new one?
ftp packages (client/server) are available: http://www.esiee.fr/puffin
> 
> Does the new xc fix major problems or is it just a a little update ?
>    IMHO there was a lot done for parisc64, but also for parisc(32) ?
We agree but it is our reason to work, isn't it? 

Here ends what we could answer. Good Luck to all :)

ESIEE Team

  parent reply	other threads:[~2001-02-06 22:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06 17:31 [parisc-linux] Generic Parisc Linux Kernel Questions & 9000/730 success report M. Grabert
2001-02-06 20:22 ` Grant Grundler
2001-02-06 21:14   ` Alex deVries
2001-02-06 22:07   ` Richard Hirst
2001-02-07  7:59     ` [parisc-linux] //strace// " Christoph Plattner
2001-02-07 12:41       ` Richard Hirst
2001-02-07 13:25         ` Christoph Plattner
2001-02-07 14:20           ` Richard Hirst
2001-02-07 23:08       ` Alan Modra
2001-02-08 22:42         ` [parisc-linux] //strace// Generic Parisc Linux Kernel Questions& " Christoph Plattner
2001-02-08 23:55           ` Richard Hirst
2001-02-09  0:10           ` Alan Modra
2001-02-06 22:12 ` Thomas Marteau [this message]
2001-02-07  0:26   ` [parisc-linux] Generic Parisc Linux Kernel Questions & " Helge Deller

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=3A8076D8.CF5E8CCD@esiee.fr \
    --to=marteaut@esiee.fr \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=xam@deathsdoor.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