svn(a)coreboot.org writes:
> Author: stepan
> Date: 2008-08-20 11:17:30 +0200 (Wed, 20 Aug 2008)
> New Revision: 3529
>
> Modified:
> trunk/coreboot-v2/targets/tyan/s2912_fam10/Config-abuild.lb
> Log:
> this port seems somehow broken.. Now, is it using FAILOVER, or is it not?!
Hmm. This was supposed to be more or less equivalent to the approach
taken by the serengeti_cheetah_fam10 target, but I see it isn't quite...
It works as it is (was), but I can have a look at it again if there are
stylistic issues. I might not have exercised the abuild file, though --
what would be the recommended way of doing that so as to ensure that is
in correspondence with the regular config file?
--
Arne.
Greetings,
Noticing that the main community of users for Artec Group's LPC dongle
has been at Coreboot, I have two announcements to make:
1) The current LPC dongle model is EOL. Some components no longer exist
on the market so, after the batch we're producing this month, it's gone.
2) We're already working on a new LPC dongle to replace the current one.
In conjunction with item #2 above, we are hereby giving the Coreboot
community an opportunity to influence the design of this new product.
While we cannot guarantee that every idea submitted will be used, we
will definitely be reading all the feedback we receive.
The end result will be an even better LPC dongle that serves the growing
needs of the embedded hardware developer community.
To compare with the current dongle design, see:
http://artecgroup.myshopify.com/products/programmable-lpc-dongle
Looking forward to receiving your ideas for this new LPC dongle product.
Best Regards,
--
Martin-Éric Racine
Business Development Manager
Artec Group OÜ
Hi,
I have a S2912 system that I'd like to run coreboot on. As I understand
it, both the S2912 and Fam10h is supported seperately, but some porting
is required to make the combination work. I'd like to work on getting
this configuration operational. If anyone has any pointers on how to
tackle it, that would be more than welcome.
Thanks in advance,
--
Arne.
Is there a magic number for LZMA? Should there be?
I accidentally used an uncompressed payload with v2 when it expected a
compressed payload, and it gave me the message:
Decoder scratchpad too small!!
Decoding error = 1
I think it would be nicer to have an error like:
Payload not compressed with lzma!
Myles