Target candidate: Dell Latitude E4300

[persmule]

Hi,

I have found a potential target Dell Latitude E4300 for libreboot (and
coreboot), for its similarity with Thinkpad X200S and X200T.

This one uses GS45, with (S)P9X00 family cpu (its sibling model e4200
uses SU family cpu), like the X200S and X200T which is supported in
coreboot (and libreboot) with gerrit's patch. And not like Latitude
E6400, this model uses DDR3 RAM (more like X200S/T).

This model uses SMSC FDC37M602, which is already supported with coreboot.

Because the succeed for GS45 in X200S/T, I think it's a good porting
target for coreboot and libreboot.

I managed to get the firmware layout with flashrom(1), which is attached
with stdout of flashrom. May they be useful to you.

What does the community think about this? Worth it?

And, waiting for certain goods' arrival, I plan to disassemble my E4300
to cleanse its cooler and heatsink, and siphon out the whole BIOS image,
which will be sent to you soon, too.

Regards,
Persmule.

[ron minnich]

On Mon, Feb 29, 2016 at 2:53 PM persmule  wrote:
> , and siphon out the whole BIOS image,
> which will be sent to you soon, too.

I am not sure what you mean by "sent to you soon", but if it means you are
going to read a copyrighted image out of firmware and mail it to us, please
do NOT do that.

thanks

ron

Logs storage? Was: Target candidate: Dell Latitude E4300

[Denis 'GNUtoo' Carikli]

On Tue, 1 Mar 2016 06:51:37 +0800
persmule  wrote:
> [dell_e4300_bios_flashrom.log  text/x-log (42687 bytes)]
> [dell_e4300_bios.layout  text/plain (135 bytes)]

Hi,

What do you think about storing devices's log obtained while running the
stock boot firmware somewhere?

Before having laptops supported in coreboot, something like that was
attempted at:
https://www.coreboot.org/Laptop

However having a repository of logs of supported and unsupported devices
would make sense.

The supported devices's log could be used to compare them with the
board-status repository.

Denis.

Logs storage? Was: Target candidate: Dell Latitude E4300

[Martin Roth]

I think that having OEM BIOS logs from supported boards does make a lot of
sense, but when I talked to Stefan about it before, he didn't want to add
unsupported boards.  His thinking was that we didn't want to be the world's
largest lspci database, which seems reasonable to me.  I'd even support
submitting them at the same time as the first commit for a mainboard went
into gerrit, but I don't think a board should be submitted when there's
absolutely nothing in coreboot yet.

I've already put some various logs into the board status tree.  I can post
the script that I use to generate these.  It already looks for coreboot vs
non-coreboot BIOS to determine which tests to run.
https://review.coreboot.org/gitweb/cgit/board-status.git/tree/gigabyte/ga-b7...

are you thinking of putting them someplace like an oem_bios_logs directory
under the mainboard?
.../tree/gigabyte/ga-b75m-d3h/oem_bios_logs/2015-12-26T19_53_49Z

Martin

On Thu, Mar 17, 2016 at 1:46 PM, Denis 'GNUtoo' Carikli 
wrote:
> On Tue, 1 Mar 2016 06:51:37 +0800
> persmule  wrote:
> > [dell_e4300_bios_flashrom.log  text/x-log (42687 bytes)]
> > [dell_e4300_bios.layout  text/plain (135 bytes)]
>
> Hi,
>
> What do you think about storing devices's log obtained while running the
> stock boot firmware somewhere?
>
> Before having laptops supported in coreboot, something like that was
> attempted at:
> https://www.coreboot.org/Laptop
>
> However having a repository of logs of supported and unsupported devices
> would make sense.
>
> The supported devices's log could be used to compare them with the
> board-status repository.
>
> Denis.