From: Ralf Baechle <ralf@oss.sgi.com>
To: Girish Gulawani <girishvg@yahoo.com>
Cc: "MIPS/Linux List (SGI)" <linux-mips@oss.sgi.com>
Subject: Re: MIPS/Linux NonSGI
Date: Sun, 3 Feb 2002 09:32:53 +0100 [thread overview]
Message-ID: <20020203093253.J20021@dea.linux-mips.net> (raw)
In-Reply-To: <007001c1a97a$6e52a9e0$c1900dd3@gol.com>; from girishvg@yahoo.com on Wed, Jan 30, 2002 at 07:39:41PM +0900
On Wed, Jan 30, 2002 at 07:39:41PM +0900, Girish Gulawani wrote:
> could solve the disk corruption problem, thanks to you. it was due to my
> over-confident source code for bus mastering device. while re-targeting the
> driver from vxworks to linux i had introduced a bug. its all working great
> now. thanks again. while this problem is solved i have one more query.
>
> as i mentioned earlier, our core supports page size of 16K. hence the mmu
> code is changed accordingly, for kernel 2.4.9. but any command load fails
> giving page alignment error. seems some problem from binfmt_elf.c file. i
> have build the command, ash, using egcc-2.91.66. to change the page
> alignment the option given was "--n16384". this option is surely wrong,
> hence could you tell me what is correct option? HOW TO CHANGE PAGE ALIGNMENT
> TO 16K WHILE LINKING USER COMMANDS??
I hate to say it but at this time we don't support any other pagesize
than 4kb on MIPS. I haven't looked into details but I'd expect to hit
a number of subtle bugs when we go to a larger pagesize. So I expect
your way to be stony.
Ralf
prev parent reply other threads:[~2002-02-03 9:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 18:57 ABI for MIPS Scott A McConnell
2002-01-24 23:41 ` MIPS/Linux NonSGI Girish Gulawani
2002-01-24 23:41 ` Girish Gulawani
2002-01-25 1:45 ` Ralf Baechle
2002-01-25 17:15 ` Kevin D. Kissell
2002-01-25 17:15 ` Kevin D. Kissell
2002-01-26 7:54 ` Girish Gulawani
2002-01-26 7:54 ` Girish Gulawani
2002-01-30 10:39 ` Girish Gulawani
2002-01-30 10:39 ` Girish Gulawani
2002-02-03 8:32 ` Ralf Baechle [this message]
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=20020203093253.J20021@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=girishvg@yahoo.com \
--cc=linux-mips@oss.sgi.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 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.