corebootlaptop | 24 Oct 09:59 2014

Most Compatible Laptop and miniITX

Which $300 to $500 laptop would be the topmost pick for CoreBoot
compatibility?

I need CoreBoot to Just Work as I cannot afford the risk or time for
development. So the unit needs solid reliable support. The laptop will
boot into Linux if you're wondering but I guess CoreBoot also does
Windows.

Can be new or slightly used. I'm happy to buy one or two generations
old. Yet it needs HDMI output to drive a second 27-in. screen (as either
(a) added pixel space, "Virtual Xdim Ydim" under X11, or (b) just as
primary monitor with laptop's screen off). So video might need to be
decent. I don't really care about the size of the laptop screen itself.

I prefer AMD and/or Radeon over Intel, but only found one such laptop on
the support list. The Pavilion m6 1035dx overheats say the reviews.

I'd like to buy off-the-shelf retail. I'd love a CoreBoot guru to scour
the offerings on retail websites (BestBuy, Walmart, the usual suspects).
But mail-order warehouse vendors (NewEgg, TigerDirect) are OK. The main
need is total CoreBoot compatibility.

As long as I'm here I may as well ask about miniITX too. If the laptop
is too problematic then that's another way I can go. What's the most
compatible miniITX on the market?

Thanks for everything, CoreBoot!

--

-- 
http://www.fastmail.fm - Access all of your messages and folders
(Continue reading)

ron minnich | 23 Oct 23:07 2014
Picon

elc next year

is in dublin. How do people feel about dublin? I'm sure John Lewis
hates the idea :-). ron

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Charles Devereaux | 21 Oct 19:24 2014
Picon

x60 - question about rfkill and wwan/bluetooth status

Hello

I am quite interested in WWAN support. My previous findings were reported on http://www.coreboot.org/pipermail/coreboot/2014-September/078538.html

At the moment, using a branch based on a  libreboot5, along with patch #4056, it works quite well, but I do not have rfkill support (cf http://www.coreboot.org/pipermail/coreboot/2014-September/078542.html) or any way to turn WWAN off.

Basically, there is no WWAN rfkill entry if you do "rfkill list"

Also, I noticed that while rfkill block 0 does turn off the wifi led,  rfkill block for bluetooth does not turn turn off its led (or even echo '5-2' > /sys/bus/usb/drivers/usb/unbind)

My belief is some ACPI entries are missing to handle that.

I am going back into the ACPI table investigation, but I'm curious whether anyone has had good results with WWAN, ie :
 - if rfkill shows a WWAN entry
 - if rfkill block reduces power consumption (cf /proc/acpi/battery/BAT0/state) and turns off the LED.

I would also be interested to know if rfkill block bluetooth does turns off the LED (the power consumption change might be too low to be noticeable)

Thanks
Charles

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Marc Jones | 20 Oct 23:44 2014
Picon

coreboot.org updates

Hi!

coreboot.org is getting a little makeover. Check it out.  http://coreboot.org

You can read about why in the following blog post:
http://blogs.coreboot.org/blog/2014/10/17/coreboot-org-website-updates/

Please let us know if you see any issues or misbehaving links with the
reorganization.

Regards,
Marc

-- 
http://se-eng.com

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

ron minnich | 19 Oct 15:07 2014
Picon

using the poor man's ftrace

Assume you downloaded the spatch program, from here.
http://coccinelle.lip6.fr/distrib/coccinelle-1.0.0-rc22-bin-x86.tgz.

/root/coccinelle-1.0.0-rc22/spatch -I /root/coccinelle-1.0.0-rc22
--sp-file util/spatch/poor-ftrace.cocci src/lib/hardwaremain.c
--in-place.

is one example.

ron

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Werner Zeh | 15 Oct 19:44 2014
Picon
Picon

Re: coreboot Prague meeting - details

Hi Rudolf.

Do you know from which time the hotel is accessible on Thursday?
I just need to know if I can arrive at the hotel directly and leave my 
car there
or if I should go to the university first.

Thanks
Werner

Am 14.10.2014 um 13:31 schrieb Rudolf Marek:
> Hi all,
>
> Sorry  for the noise I managed to exchange euros already. I did a 
> favor to a colleague who needed urgently cash in CZK. If you need to 
> exchange,
> I would try either ATMs or as I have written on wiki page the 
> exchange8.cz (todays rate is 1 EUR =27.68 CZK) or any other exchange 
> office
> where is acceptable ratio and no fees.
>
> Thanks
> Rudolf
>

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Nico Huber | 13 Oct 23:50 2014
Picon
Picon

Wiki access

Hi,

looks like I don't have an account for the coreboot wiki, yet.
Well, at least I don't remember, and can't find any stale email...

Nico

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Nico Huber | 13 Oct 23:43 2014
Picon
Picon

Prague meeting: Work on USB debug

Hi folks,

I had first success with my pomona clip, today. Sadly, the mobo does
not have any UART,  so I'll finally have to switch to something more
advanced.  I've a high-speed ftdi usb adapter board that can be used
as USB debug device, but this will need some code changes along with
some refactoring.  I think, I'll focus on that during the hackathon.

It would be nice, to have some more usb debug devices available for
regression testing.

Nico

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Nico Huber | 12 Oct 20:26 2014
Picon
Picon

Re: [coreboot-gerrit] Patch merged into coreboot/master: 8414d3c xcompile: always use -march=i686

Hi folks,

something seems wrong with this one:

On 25.08.2014 23:33, gerrit <at> coreboot.org wrote:
> the following patch was just integrated into master:
> commit 8414d3c0b407d9afc6a2446dba3ca358da2c7bb6
> Author: Aaron Durbin <adurbin <at> chromium.org>
> Date:   Thu Oct 10 12:44:11 2013 -0500
> 
>     xcompile: always use -march=i686
>     
>     When compiling coreboot for x86 on gcc the compiler is
>     free to pick whatever defaults it is using at the time of
>     gcc's compile/configuration when no -march is specified.
>     Not properly specifying -march then opens up the use of SSE
>     instructions for compilation units it should not be used such
>     as the SMM module as this module doesn't save/restore SSE
>     registers.
>     
>     Change-Id: I64d4a6c5fa9fadb4b35bc7097458e992a094dcba
>     Signed-off-by: Aaron Durbin <adurbin <at> chromium.org>
>     Reviewed-on: https://chromium-review.googlesource.com/172640
>     Reviewed-by: Stefan Reinauer <reinauer <at> google.com>
>     (cherry picked from commit d49358f7959bb52c3e7ff67d37c21a1b294adf72)
>     Signed-off-by: Isaac Christensen <isaac.christensen <at> se-eng.com>
>     Reviewed-on: http://review.coreboot.org/6716
>     Tested-by: build bot (Jenkins)

I bisected a no-serial-output problem on a kontron/986lcd-m with a Core
Duo (Yonah) CPU, leading to this commit. I don't see what is going wrong
here. Core Duo is obviously kind of i686, but specifying -march=i386
works around the problem. So far I haven't spotted any differences in
generated code (other than reordering).

If I don't specify -march=, the reference toolchain seems to generate
the same code as with -march=i386. Maybe we should default to that?

Also, I was told, that if you specify -march=, the compiler may use CPU
features that have to be enabled first.

Nico

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Picon

Re: unable to build coreboot with grub

On 12.10.2014 13:30, Vipin Gahlaut wrote:
> Thanks a lot Valdimir,
> 
> After "make clean" ROM Size config changes kicked in as expected and I
> managed to build grub payload.
> 
Please keep the list CC'ed
> Thanks you very much for your help and support.
> 
> 
> 
> On Sun, Oct 12, 2014 at 4:39 PM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder <at> gmail.com <mailto:phcoder <at> gmail.com>> wrote:
> 
>     On 12.10.2014 13:03, Vipin Gahlaut wrote:
>     > Ok, I changed CONFIG_BOARD_ROMSIZE_KB_ to 512 directly in .config as
>     > this is can not be changed in menuconfig.
>     Don't. You don't need to change it at all.
>     > My .config lokks like below
>     > and it still it says 262KB is too big?
>     >
>     Always do "make clean" after config change
>     > # CONFIG_BOARD_ROMSIZE_KB_256 is not set
>     > CONFIG_BOARD_ROMSIZE_KB_512=y
>     > # CONFIG_COREBOOT_ROMSIZE_KB_64 is not set
>     > # CONFIG_COREBOOT_ROMSIZE_KB_128 is not set
>     > # CONFIG_COREBOOT_ROMSIZE_KB_256 is not set
>     > CONFIG_COREBOOT_ROMSIZE_KB_512=y
>     > # CONFIG_COREBOOT_ROMSIZE_KB_1024 is not set
>     > # CONFIG_COREBOOT_ROMSIZE_KB_2048 is not set
>     > # CONFIG_COREBOOT_ROMSIZE_KB_4096 is not set
>     > # CONFIG_COREBOOT_ROMSIZE_KB_8192 is not set
>     > # CONFIG_COREBOOT_ROMSIZE_KB_12288 is not set
>     > # CONFIG_COREBOOT_ROMSIZE_KB_16384 is not set
>     > CONFIG_COREBOOT_ROMSIZE_KB=512
>     > CONFIG_ROM_SIZE=0x80000
>     >
>     >
>     > On Sun, Oct 12, 2014 at 4:21 PM, Vladimir 'φ-coder/phcoder' Serbinenko
>     > <phcoder <at> gmail.com <mailto:phcoder <at> gmail.com>
>     <mailto:phcoder <at> gmail.com <mailto:phcoder <at> gmail.com>>> wrote:
>     >
>     >     On 12.10.2014 12:44, Vipin Gahlaut wrote:
>     >     > I tried changing under main mainboard -> rom chip size but
>     does not seem
>     >     > to be helping. If I look at .config I suspect that the reason is
>     >     > CONFIG_BOARD_ROMSIZE_KB_256=y which doesn't change even if I
>     change ROM
>     >     > size in main board.
>     >     CONFIG_BOARD_ROMSIZE_KB_* is the default used by
>     >     CONFIG_COREBOOT_ROMSIZE_KB_*
>     >
>     >
> 
> 
> 

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Picon

Re: unable to build coreboot with grub

On 12.10.2014 13:03, Vipin Gahlaut wrote:
> Ok, I changed CONFIG_BOARD_ROMSIZE_KB_ to 512 directly in .config as
> this is can not be changed in menuconfig.
Don't. You don't need to change it at all.
> My .config lokks like below
> and it still it says 262KB is too big?
> 
Always do "make clean" after config change
> # CONFIG_BOARD_ROMSIZE_KB_256 is not set
> CONFIG_BOARD_ROMSIZE_KB_512=y
> # CONFIG_COREBOOT_ROMSIZE_KB_64 is not set
> # CONFIG_COREBOOT_ROMSIZE_KB_128 is not set
> # CONFIG_COREBOOT_ROMSIZE_KB_256 is not set
> CONFIG_COREBOOT_ROMSIZE_KB_512=y
> # CONFIG_COREBOOT_ROMSIZE_KB_1024 is not set
> # CONFIG_COREBOOT_ROMSIZE_KB_2048 is not set
> # CONFIG_COREBOOT_ROMSIZE_KB_4096 is not set
> # CONFIG_COREBOOT_ROMSIZE_KB_8192 is not set
> # CONFIG_COREBOOT_ROMSIZE_KB_12288 is not set
> # CONFIG_COREBOOT_ROMSIZE_KB_16384 is not set
> CONFIG_COREBOOT_ROMSIZE_KB=512
> CONFIG_ROM_SIZE=0x80000
> 
> 
> On Sun, Oct 12, 2014 at 4:21 PM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder <at> gmail.com <mailto:phcoder <at> gmail.com>> wrote:
> 
>     On 12.10.2014 12:44, Vipin Gahlaut wrote:
>     > I tried changing under main mainboard -> rom chip size but does not seem
>     > to be helping. If I look at .config I suspect that the reason is
>     > CONFIG_BOARD_ROMSIZE_KB_256=y which doesn't change even if I change ROM
>     > size in main board.
>     CONFIG_BOARD_ROMSIZE_KB_* is the default used by
>     CONFIG_COREBOOT_ROMSIZE_KB_*
> 
> 

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Gmane