All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georg Chini <georg.chini@triaton-webhosting.com>
To: linux-kernel@vger.kernel.org
Subject: SPARC64 and 32: Several problems with 2.6.0-test5 and test6
Date: Sun, 05 Oct 2003 22:41:58 +0200	[thread overview]
Message-ID: <3F808216.3090106@triaton-webhosting.com> (raw)

Hello,

I did some testing with test5 and test6 kernels on
my Sparc Ultra1 and Sparcstation 5. Here is a summary
of the problems I observed. Maybe this helps to fix
things.

1) Keyboard:
    On both architectures the Sun type 5 keyboard
    (and mouse) will not be found.

2) Console:
    On both architectures only PROM-console will work. The
    system will not switch to serial (Ultra1) or TCX (SS5)
    console.
    Sending break gives no ok-prompt.

3) Netfilter on sparc64:
    Any iptables command except iptables -L crashes my
    system without further messages. I am already in contact with
    Harald Welte about this (see netfilter-devel list).

4) Compile on sparc32
    The function sched_clock is missing in time.c.
    There is a posting by Andrew Morton on this list
    which defines the function. The kernel compiles
    and boots with this patch.
    When compiling modules I get following unresolved
    symbols in various modules in stage 2:

   .div
   .rem
   .udiv
   .umul
   .urem
   ___atomic_add
   ___atomic_sub
   ___clear_bit
   ___set_bit
   prom_apply_generic_ranges
   prom_halt
   prom_printf
   sparc_flush_page_to_ram
   sun_do_break

    I think I could fix this myself if anyone can tell me where
    to find an example.

    Regards
            Georg Chini


             reply	other threads:[~2003-10-05 20:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-05 20:41 Georg Chini [this message]
2003-10-05 22:19 ` SPARC64 and 32: Several problems with 2.6.0-test5 and test6 David S. Miller

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=3F808216.3090106@triaton-webhosting.com \
    --to=georg.chini@triaton-webhosting.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.