From: Jesse Barnes <jbarnes@sgi.com>
To: linux-kernel@vger.kernel.org, pazke@orbita1.ru
Subject: Re: [PATCH][RFC] SGI VISWS support for 2.5
Date: Thu, 20 Jun 2002 14:37:43 -0700 [thread overview]
Message-ID: <20020620213743.GA67049@sgi.com> (raw)
In-Reply-To: <20020620112608.GA303@pazke.ipt>
I gave it a go on a 320 that I have here and it gets into start_kernel
somewhere, but I don't get any output on the serial console. If you'd
like to get it into 2.5, maybe we should clean it up a little first
(as well as get it working)?
When I ported the last patch forward to 2.4.17, I noticed that there
were quite a few parts that could use some work. Looking through the
patch, it seems like the head.S stuff could be done in a better way,
maybe a seperate head.S for machines that start in protected mode?
Then again, maybe the boot loader should just be changed? The
interrupt handler code also needs to be fixed up.
I haven't looked at the patch to seperate out i386 subarches yet, but
maybe that would be a good first step to abstracting away some of the
visws setup code?
Jesse
On Thu, Jun 20, 2002 at 03:26:08PM +0400, Andrey Panin wrote:
> Hi all,
>
> attached patch is a forward port of latest (2.4.17) visws patch from
> sourceforge. It's mostly trivial textual merge. Builds, unteseted.
>
> Please take a look at it.
>
> --
> Andrey Panin | Embedded systems software engineer
> pazke@orbita1.ru | PGP key: wwwkeys.eu.pgp.net
next prev parent reply other threads:[~2002-06-20 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 11:26 [PATCH][RFC] SGI VISWS support for 2.5 Andrey Panin
2002-06-20 18:22 ` Jesse Barnes
2002-06-20 19:38 ` James Simmons
2002-06-20 21:37 ` Jesse Barnes [this message]
2002-06-21 11:14 ` Andrey Panin
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=20020620213743.GA67049@sgi.com \
--to=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pazke@orbita1.ru \
/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.