Rafael Vanoni wrote:
>> Please explain why you want to modify these values at run time?
>
> Like I said in a previous post, I'd like to set fields like version,
> serial number on a per system basis.
That's not the why, that's the what. Indeed you already wrote what
you want.
I'm asking *why* you
As Mike mentioned earlier, you need the TXE ( located in top 6MB ) from
BYT-I_SEC_DUAL_BOOT_PV_GOLD.
The TXE from the BIOS’s you mentioned don’t work with coreboot. I ran into the
same issue as you.
Alternatively you can erase the top 6MB to start in non-descriptor mode. I
don’t think this matte
PCI ids will be different. Plus some devices may be disabled.
On Jun 20, 2014 5:21 PM, "Gerald Otter" wrote:
> As Mike mentioned earlier, you need the TXE ( located in top 6MB ) from
> BYT-I_SEC_DUAL_BOOT_PV_GOLD.
> The TXE from the BIOS’s you mentioned don’t work with coreboot. I ran into
> the
> PCI ids will be different
Oh - what do you mean by the Sean?
I am still trying to understand why for two identical CPUID/Stepping E3815s,
with the same 8BM flash image, I get different PCI device ids for the Soc
Transaction Router ( rather than 0f00 ) and Video ( 0031 rather than 0f00
)
Dave, I was ready to boot your
suggestion and the hardware guys said:
"We know there's no clock", then soon after had it booting
normally.
Good call. This was indeed a debugging session, not a coreboot
issue.
A bit of history. Our design
hi,
i did some experiments with the baytrail fsp coreboot and first of all i
like to say thanks for all the good code! everything looks much better than
the last time i tried to do anything with coreboot.
for the problems - maybe there is something wrong with reading the ids. i
found that on my p
On 06/20/2014 01:25 AM, Peter Stuge wrote:
Rafael Vanoni wrote:
Please explain why you want to modify these values at run time?
Like I said in a previous post, I'd like to set fields like version,
serial number on a per system basis.
That's not the why, that's the what. Indeed you already wr
Am 20.06.2014 22:01, schrieb Rafael Vanoni:
> Take serial number, for example. I'd like each different system that I
> build to have its own serial number, and building coreboot for every
> serial number doesn't scale.
We have an .id section just below the 16bit entry point - that can
(easily) be e
On 20.06.2014 20:08, Patrick Georgi wrote:
> Am 20.06.2014 22:01, schrieb Rafael Vanoni:
>> Take serial number, for example. I'd like each different system that I
>> build to have its own serial number, and building coreboot for every
>> serial number doesn't scale.
> We have an .id section just be
Am 20.06.2014 22:40, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
> (think MAC address).
I guess PC technology is finally beyond requiring those at fixed magic
offsets. Some of our chipsets still need it that way.
> having fixed indexes doesn't scale.
Neither do text files.
Patrick
signatur
realistically, though, it's hard for me to see how setting the serial # at
firmware image build time scales. And setting it after boot makes no real
sense either -- it's not really a serial number if you're changing it at
that point.
But some way to customize the binary images with a serial number
On 20.06.2014 20:43, Patrick Georgi wrote:
> Am 20.06.2014 22:40, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
>> (think MAC address).
> I guess PC technology is finally beyond requiring those at fixed magic
> offsets. Some of our chipsets still need it that way.
>
>> having fixed indexes doesn'
If we figure out why we see the device id of 0x for the SOC
transaction router, I'd really like to understand that. I had initially
thought it was a B0 vs B3 issue, but I've heard from people that it
happens on the B3 silicon as well.
Currently if the device id comes up as 0, the northclus
Hi,
I'm getting ready to push some code that better aligns things between
the Kconfig option and the FSP for the MMIO configuration area. It
shouldn't be a problem after that.
Martin
On 06/20/2014 01:17 PM, Karl-Heinz Nirschl wrote:
hi,
i did some experiments with the baytrail fsp coreboot
Dear Sir
I would like to migrate my PC to a free BIOS. Do I have to replace the
motherboard, please?
Thanks
Kevin
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
ron minnich [mailto:rminn...@gmail.com] wrote:
]realistically, though, it's hard for me to see how setting the
]serial # at firmware image build time scales. And setting it after
]boot makes no real sense either -- it's not really a serial number
]if you're changing it at that point.
]But some w
On Fri, Jun 20, 2014 at 10:00 PM, Scott Duplichan wrote:
>
>
> Putting the serial number in the same flash chip as the main
> firmware is a cost reduction measure used with desktop and other
> low cost boards. I have even seen a board where the MAC address
> lives there. The only protection for t
Am 21.06.2014 08:06, schrieb ron minnich:
> very interesting. Thing is, this is pretty much the antithesis of
> build-time serial number creation ... which is the thing that I don't
> see scaling.
Right now we compile any serial number right into .text, and modifying
that is not a good idea (plus,
On Fri, Jun 20, 2014 at 11:20 PM, Patrick Georgi
wrote:
>
>
> In the end, I pose the question why a serial number must be exported to
> the OS in the first place - this looks like a potential privacy issue to
> me, while doing nothing for servicing the part (if it's sent back, read
> the bar code
A coreboot@coreboot.org subscriber wrote:
]Hi Scott,
]
]It appears they are looking for a full-time position. If they were
]willing to outsource, I would be interested.
It might be useful to apply anyway. Others have pointed out
that most of the coreboot experts are located in Europe.
If a few e
20 matches
Mail list logo
