On 7/29/13 11:43 PM, Eugen Leitl wrote:
On Tue, Jul 30, 2013 at 02:40:16AM +0200, Stefan Reinauer wrote:
I agree with Alex: If you are concerned by this issue, please make an
effort to fix it. It would be great to bring the clear level of
separation that we have on newer systems to older CPU
On Tue, Jul 30, 2013 at 2:39 AM, Stefan Reinauer
stefan.reina...@coreboot.org wrote:
No, but it comes with an 8k signed, binary primary bootloade that loads
coreboot from flash.
in other words, the days when we could have 0 binary blobs are fast ending.
I don't like that either. But I don't
On 07/30/13 18:43, ron minnich wrote:
On Tue, Jul 30, 2013 at 2:39 AM, Stefan Reinauer
stefan.reina...@coreboot.org wrote:
No, but it comes with an 8k signed, binary primary bootloade that loads
coreboot from flash.
in other words, the days when we could have 0 binary blobs are fast ending.
* Alex G. mr.nuke...@gmail.com [130725 22:23]:
Denis,
We have in place a pretty darn good infrastructure of separating the
microcode from the coreboot stages. It's very easy to store microcode as
a _separate_ CBFS file. Not all CPUs use this, but changing this is
trivial. Patches welcome.
On Wed, Jul 24, 2013 at 03:51:55PM +0400, Nikita Karetnikov wrote:
Would you like to try that? I'm willing to help if it's somehow
possible with QEMU (and without proprietary programs). What
instructions should be used? Could you provide a step-by-step guide?
I don't think you can do this
On 07/22/2013 01:25 PM, Denis 'GNUtoo' Carikli wrote:
On Mon, 15 Jul 2013 08:14:22 -0700
ron minnich rminn...@gmail.com wrote:
I don't see how excluding the new, fixed version from coreboot helps
anything. Further, it means you don't have bug-fixed microcode, which
seems bad.
It is at
Looking at what I wrote on the wiki:
CPU Microcode (optional?)
Basicaly the issue is that I found that the microcode was included,
trough #include and headers containig its code in coreboot,
What that means is that even if you select to use no microcode in make
menuconfig, it will still be
On Mon, Jul 22, 2013 at 11:25 AM, Denis 'GNUtoo' Carikli
gnu...@no-log.org wrote:
It is at least a licensing problem:
That microcode has a proprietary license in its header,
with some terms that are incompatible with the GPLv2...
And coreboot is released under the GPLv2.
Given the effort
On Mon, 15 Jul 2013 08:14:22 -0700
ron minnich rminn...@gmail.com wrote:
I don't see how excluding the new, fixed version from coreboot helps
anything. Further, it means you don't have bug-fixed microcode, which
seems bad.
It is at least a licensing problem:
That microcode has a proprietary
On Sun, Jul 14, 2013 at 7:58 AM, Denis 'GNUtoo' Carikli
gnu...@no-log.org wrote:
What is unclear and must be tested is if the computer would boot or
have some issues without the microcode. It really has to be tested...
It might also work only on a subset of the X60/T60.
But the microcode is
Hi,
On Sat, 13 Jul 2013 22:18:50 +0400
Nikita Karetnikov nik...@karetnikov.org wrote:
I mentioned Thinkpads for two reasons: I thought they don't need
proprietary components, and they are quite popular among Coreboot
people.
[1]
If somebody wants a laptop with coreboot today, that has vendor
support, get an acer c7 chromebook. If you can stand the keyboard,
which you really want to test. But it's an incredible deal.
What do you mean by vendor support? Does it require any non-free
components? Does it come with
How do you want to help? You can get a Thinkpad right now, with the best
coreboot has to offer, knowing full well it isn't 100% free (yet).
Well, I'm still not sure about that. Could you elaborate on non-free
components? This page [1] is not clear about microcode, for instance.
You can
I'm looking for an x86_64 laptop to try Coreboot. I've looked through
the archives [1,2] and the wiki [3]; it seems the most popular machines
are x60s and t60.
However, these machines are shipped in different configurations [4,5].
This page [6] mentions Core Duo Mobile L2300, which has a 32-bit
On 12-07-13 12:35, Nikita Karetnikov wrote:
I'm looking for an x86_64 laptop to try Coreboot. I've looked through
the archives [1,2] and the wiki [3]; it seems the most popular machines
are x60s and t60.
Which (again) strikes me as ood, that intel laptops are the most
recommended ones.
The
It's kind of useless to point to a bunch of random laptops with a
compatible chipset. It's never that simple. You don't know what the EC
is or how to talk to it, and you don't have critical info you need to
really make this work. So count on about a year of effort,
potentially. What if there's a
On Fri, Jul 12, 2013 at 9:42 AM, ron minnich rminn...@gmail.com wrote:
It's kind of useless to point to a bunch of random laptops with a
compatible chipset. It's never that simple. You don't know what the EC
is or how to talk to it, and you don't have critical info you need to
really make
17 matches
Mail list logo
