Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Marc St-Jean <Marc_St-Jean@pmc-sierra.com>
Cc: Andrew Sharp <tigerand@gmail.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH 2/5] mips: PMC MSP71xx mips common
Date: Tue, 27 Feb 2007 17:38:41 +0000	[thread overview]
Message-ID: <20070227173841.GD12230@networkno.de> (raw)
In-Reply-To: <45E465C1.50408@pmc-sierra.com>

Marc St-Jean wrote:
[snip]
> >  > +#ifdef CONFIG_PMC_MSP
> >  > +     jal     kernel_entry
> >  > +#else

Maybe introduce a CONFIG_BOOT_RAW (and use it in arch/mips/Makefile
to objcopy the kernel to a raw binary).

> >  > +     /*
> >  >        * Reserved space for exception handlers.
> >  >        * Necessary for machines which link their kernels at KSEG0.
> >  >        */
> >  >       .fill   0x400
> >  > +#endif /* CONFIG_PMC_MSP */
> > 
> > This is getting kind of ugly.  There are a whole lot of config choices
> > that need to use the 'j kernel_entry'.  Do they all have to have their
> > own?  I'm not sure what the best way is to handle them all.
> 
> I agree but don't know the best way to handle this. I could introduce a
> SYS_NO_EXEPT_FILL or similar flag but this seems excessive.
> 
> Any other ideas from arch/mips folks?

Something like

#if LOADADDR == 0xffffffff80000000
	.fill	0x400
#endif

but by defining an appropriate name in arch/mips/Makefile instead of
externalizing the load-y/LOADADDR there.


Thiemo

  reply	other threads:[~2007-02-27 17:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 17:09 [PATCH 2/5] mips: PMC MSP71xx mips common Marc St-Jean
2007-02-27 17:38 ` Thiemo Seufer [this message]
2007-02-28 19:32   ` Ralf Baechle
2007-02-27 18:46 ` Andrew Sharp
2007-02-28 19:42   ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2007-03-16 23:53 Marc St-Jean
2007-03-17  0:46 ` Ralf Baechle
2007-03-07 18:01 Marc St-Jean
2007-03-16  1:58 ` Ralf Baechle
2007-03-01 20:41 Marc St-Jean
2007-02-28 22:35 Marc St-Jean
2007-02-28 21:35 Marc St-Jean
2007-02-28 21:43 ` Uhler, Mike
2007-02-28 21:43   ` Uhler, Mike
2007-02-28 22:18 ` Ralf Baechle
2007-02-28  0:04 Marc St-Jean
2007-02-27 21:27 Marc St-Jean
2007-02-28 19:52 ` Ralf Baechle
2007-02-27 17:59 Marc St-Jean
2007-02-27 20:03 ` Thiemo Seufer
2007-02-27  0:12 Marc St-Jean
2007-02-27  0:43 ` Andrew Sharp
2007-02-23 21:27 Marc St-Jean
2007-02-23 21:15 Marc St-Jean
2007-02-23 20:53 Marc St-Jean
2007-02-23 21:02 ` Sergei Shtylyov
2007-02-23 21:02 ` David Daney
2007-02-23 19:56 Marc St-Jean
2007-02-23 20:35 ` Sergei Shtylyov

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=20070227173841.GD12230@networkno.de \
    --to=ths@networkno.de \
    --cc=Marc_St-Jean@pmc-sierra.com \
    --cc=linux-mips@linux-mips.org \
    --cc=tigerand@gmail.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