Hello,
On the LinuxBIOS website I see several references to remote
flashing. Is there any documentaion, or can someone point me in the
right direction on how to set this up?
Thanks - Joe
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
* Joseph Smith [EMAIL PROTECTED] [070719 11:49]:
Hello,
On the LinuxBIOS website I see several references to remote
flashing. Is there any documentaion, or can someone point me in the
right direction on how to set this up?
Log in to a remote system and use the flashrom utility from
I want to set a value in the epia-m southbridge Generic Power
Management Register.
Is this possible? In the source code of the vt8253 I see only Value
Settings to the Bus Control Register.
you'll need to look at the chip.h for the part, see how it relates to
the code, and take it
Ok, I've found a solution:
setpci -s 0:11.0 4f.b=9
not very nice, but it works
// marcel
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
On Sun, Jul 15, 2007 at 12:30:48PM -0700, ron minnich wrote:
2 interesting news items.
[..]
We're getting there!
Indeed. Thank you everyone for making a great effort!
//Peter
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
This didn't turn out to be as enlightening as I hoped. I think that I
put it into the correct Makefile.
Marc
--
Marc Jones
Senior Software Engineer
(970) 226-9684 Office
mailto:[EMAIL PROTECTED]
http://www.amd.com/embeddedprocessors
Make .map files for the different portions of V3.
Author: mjones
Date: 2007-07-19 17:03:05 +0200 (Thu, 19 Jul 2007)
New Revision: 458
Modified:
LinuxBIOSv3/include/lar.h
LinuxBIOSv3/lib/lar.c
Log:
Add execute in place to lar. Allows code to be run from the ROM.
Signed-off-by: Marc Jones [EMAIL PROTECTED]
Acked-by: Ronald G. Minnich
ron minnich wrote:
Acked-by: Ronald G. Minnich [EMAIL PROTECTED]
r458
Thanks,
Marc
On 7/18/07, Marc Jones [EMAIL PROTECTED] wrote:
:)
Marc
--
Marc Jones
Senior Software Engineer
(970) 226-9684 Office
mailto:[EMAIL PROTECTED]
http://www.amd.com/embeddedprocessors
Add
* Marc Jones [EMAIL PROTECTED] [070719 16:59]:
This didn't turn out to be as enlightening as I hoped. I think that I put
it into the correct Makefile.
Yeah.
Please wait with checking this in. I made a similar patch which adds a
little more stuff (adding nm to .xcompile, adding dependencies,
Author: mjones
Date: 2007-07-19 17:15:57 +0200 (Thu, 19 Jul 2007)
New Revision: 459
Modified:
LinuxBIOSv3/arch/x86/geodelx/stage0.S
LinuxBIOSv3/arch/x86/geodelx/stage1.c
LinuxBIOSv3/arch/x86/mc146818rtc.c
LinuxBIOSv3/arch/x86/stage1.c
LinuxBIOSv3/include/mc146818rtc.h
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
* Marcel Graber [EMAIL PROTECTED] [070719 14:42]:
Ok, I've found a solution:
setpci -s 0:11.0 4f.b=9
not very nice, but it works
Does reboot work with that?
--
coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
Tel.: +49 761 7668825 • Fax: +49 761 7664613
Email: [EMAIL
setpci -s 0:11.0 4f.b=9
not very nice, but it works
Does reboot work with that?
Yes, I set this command in my /sbin/reboot
//marcel
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/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
This is a simple example how to statically link printk into initram.
It grows initram by incredible 2000 bytes here. So yes, this is a
solution for now.
Signed-off-by: Stefan Reinauer [EMAIL PROTECTED]
Index: mainboard/emulation/qemu-x86/Makefile
* 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
Hi
Wonderful gcc-isms :-) I learned something new today that I want to
share.
This one warns about printk parameters.
I don't claim we should check this in, but we should at least fix the
warnings it brings..
Signed-off-by: Stefan Reinauer [EMAIL PROTECTED]
Index: include/console.h
* 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
Acked-by: Ronald G. Minnich [EMAIL PROTECTED]
if you wish to commit. I think this is acceptable for the short term.
ron
On 7/19/07, Stefan Reinauer [EMAIL PROTECTED] wrote:
This is a simple example how to statically link printk into initram.
It grows initram by incredible 2000 bytes here. So
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
2007/7/20, john [EMAIL PROTECTED]:
ST wrote:
Hi John
Please use the linuxbios list for inquiries.
1. Can you tell me which bios chip is enabled by each wire jumper? The
two wires are called #1 and #3 but which enables original bios and which
enables new bios on plcc-32 socket? On your
30 matches
Mail list logo
