* ron minnich [EMAIL PROTECTED] [070720 06:45]:
we want stage2 printk and other code to use the stage0 support code
because stage 0 has done some setup -- there is some state there --
that we'd like stage 2 to inherit. I think.
Not sure what state you mean.
If it is only about state, we could
On 7/19/07, Stefan Reinauer [EMAIL PROTECTED] wrote:
* ron minnich [EMAIL PROTECTED] [070720 06:45]:
we want stage2 printk and other code to use the stage0 support code
because stage 0 has done some setup -- there is some state there --
that we'd like stage 2 to inherit. I think.
Not sure
ron minnich wrote:
Acked-by: Ronald G. Minnich [EMAIL PROTECTED]
I will try to look at your other problem tomorrow.
ron
r459
Thanks,
Marc
--
Marc Jones
Senior Software Engineer
(970) 226-9684 Office
mailto:[EMAIL PROTECTED]
http://www.amd.com/embeddedprocessors
--
linuxbios
Marc Jones wrote:
This patch gets Geode LX into initram. It also cleans up some of the
generic stage0 and stage1 code for getting through CAR and initram.
At this point I need some help. We get into initram but I think that
there is a link problem where the first function call to
On Thursday 19 July 2007 21:59, Marc Jones wrote:
Marc Jones wrote:
This patch gets Geode LX into initram. It also cleans up some of the
generic stage0 and stage1 code for getting through CAR and initram.
At this point I need some help. We get into initram but I think that
there is a
On 7/19/07, Juergen Beisert [EMAIL PROTECTED] wrote:
Initram should run at the address it was linked to.
A very key point since LAR and linking are not connected, by design.
I think this is why I was so unsure about XIP, then I forgot it.
ron
--
linuxbios mailing list
On Thursday 19 July 2007 22:38, ron minnich wrote:
initram is XIP, right?
The LAR files we have run have all been linked at 0x0 base, i.e. where
they would be copied to to run. I would bet the ld step is initram is
the same.
So, here's a problem. XIP in LAR is problematic, because your
On Thursday 19 July 2007 23:11, ron minnich wrote:
On 7/19/07, Juergen Beisert [EMAIL PROTECTED] wrote:
Initram should run at the address it was linked to.
A very key point since LAR and linking are not connected, by design.
I think this is why I was so unsure about XIP, then I forgot it.
ron minnich wrote:
On 7/19/07, Juergen Beisert [EMAIL PROTECTED] wrote:
Initram should run at the address it was linked to.
A very key point since LAR and linking are not connected, by design.
I think this is why I was so unsure about XIP, then I forgot it.
ron
I only think
* ron minnich [EMAIL PROTECTED] [070719 22:38]:
So, here's a problem. XIP in LAR is problematic, because your location
in lar affects the linking step.
now what?
In favor of a good design we should have a defined API between stage0
and any other stages and set up a vector table with the
* Marc Jones [EMAIL PROTECTED] [070719 23:52]:
I only think that this is a problem with initram because it links to
stage0. Maybe we should reconsider that. Maybe it needs to stand alone.
Marc
There are a few functions that we might want to share:
- printk
- the lar functions (?? not sure,
Stefan Reinauer wrote:
* Marc Jones [EMAIL PROTECTED] [070719 23:52]:
I only think that this is a problem with initram because it links to
stage0. Maybe we should reconsider that. Maybe it needs to stand alone.
Marc
There are a few functions that we might want to share:
- printk
how about for now, let's just have initram with its own copy of
things, and then let the others link against stage 0 as usual.
I've done the 'vector table' approach a fair number of times. It
eventually tends to run into trouble as more and more junk gets packed
into it.
But, we can argue that
* Marc Jones [EMAIL PROTECTED] [070720 00:34]:
Modular design and it's advantages and disadvantages. I think we should
try to go the defined interface to stage0 way, as Juergen also
suggested (I dont think this is a hack)
If it is only for printk then I don't think it is worth it. I
* ron minnich [EMAIL PROTECTED] [070720 00:47]:
I've done the 'vector table' approach a fair number of times. It
eventually tends to run into trouble as more and more junk gets packed
into it.
This is not a general weakness of the approach. Junk sneaking in is even
easier when you link and it
we want stage2 printk and other code to use the stage0 support code
because stage 0 has done some setup -- there is some state there --
that we'd like stage 2 to inherit. I think.
ron
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
This patch gets Geode LX into initram. It also cleans up some of the
generic stage0 and stage1 code for getting through CAR and initram.
At this point I need some help. We get into initram but I think that
there is a link problem where the first function call to post_code() is
past the
Acked-by: Ronald G. Minnich [EMAIL PROTECTED]
I will try to look at your other problem tomorrow.
ron
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
18 matches
Mail list logo
