| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| | |
X200 can now be built with either SeaBIOS or GRUB as a default
payload, e.g.:
'./libreboot build coreboot x200 textmode 16mb seabios'
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These configurations will be read and supplied to make as
command-line arguments and override those defined in the config at
projects/coreboot/configs/x200/config
X200 Coreboot ROMs can be built with, e.g.:
'./libreboot build coreboot x200 corebootfb 8mb'
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The corebootfb ROM will use Coreboot's framebuffer for display while
the textmode ROM will use the legacy VGA text mode which is necessary
for payloads such as Memtest86+.
Options (and their values) changed in the new corebootfb config:
CONFIG_GENERIC_LINEAR_FRAMEBUFFER=y
CONFIG_LINEAR_FRAMEBUFFER=y
X200 Coreboot ROMs can now be built with
'./libreboot build coreboot x200 corebootfb' or
'./libreboot build coreboot x200 textmode', respectively.
|
|/
|
|
|
| |
The 8mb X200 config from projects/coreboot/configs/x200_8mb/config
is used as the base config for the x200 target.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
T400 (and variants) can now be built with either SeaBIOS or GRUB
as default payloads, e.g.:
'./libreboot build coreboot t400 textmode 16mb seabios'
|
|/ |
|
|\ |
|
| | |
|
|\ \
| |/
|/| |
|
|/ |
|
|\ |
|
| | |
|
|\ \
| | |
| | |
| | | |
master
|
| | | |
|
| | | |
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Currently it is impossible to boot from USB devices on the KFSN4-DRE.
Apparently neither GRUB nor SeaBIOS recognizes attached USB mass
storage (according to Timothy Pearson).
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The base configuration for a given board can be overriden by config
files (also named "config") placed into target-specific
subdirectories.
These additional configurations are read and passed to make as
arguments, overriding their counterparts in the base config file;
consquently, commented lines should not be added to these configs.
R400/T400/T500/W500 ROMs may now be built for 4/8/16mb flash chip
sizes.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
project_file_path() now returns the first matching path rather than
the last. This is necessary to allow splitting up configuration
files for projects into "base" and "overriding" configs.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These configurations are intended to be read and supplied to make as
command-line arguments and override those defined in the config at
projects/coreboot/configs/{corebootfb,textmode}/config
For now, these configs do nothing--subsequent commits will add this
overriding functionality.
T400 Coreboot ROMs can be built with
'./libreboot build coreboot t400 corebootfb 8mb', for example, though
the last argument specifying flash chip size does nothing currently.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The corebootfb ROM will use Coreboot's framebuffer for display while
the textmode ROM will use the legacy VGA text mode which is necessary
for payloads such as Memtest86+.
Options (and their values) changed in the new corebootfb config:
#CONFIG_VGA_TEXT_FRAMEBUFFER is not set
CONFIG_GENERIC_LINEAR_FRAMEBUFFER=y
CONFIG_LINEAR_FRAMEBUFFER=y
T400 Coreboot ROMs can now be built with
'./libreboot build coreboot t400 corebootfb' or
'./libreboot build coreboot t400 textmode', respectively.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The goal here is to have fewer full configuration files.
By consolidating the T400 board configs (and board variants such as
the R400/T500/W500) into at most two base configs we can rely on
separate target-specific configs (e.g., for different flash sizes) to
override our default values given in
projects/coreboot/configs/t400/config
File contents of the new configs located at
projects/coreboot/t400/variants/ are now supplied to make as
command-line arguments, overriding the same configurations in the
base config. The T400 file is included as an example of which
configurations need to be overriden by a variant for a proper
SMBIOS name to be used.
Configs allowing for different ROM chip sizes other than the default
are reimplemented in a subsequent commit.
The following are no longer valid targets when building Coreboot:
r400_16mb
r400_8mb
r400_4mb
t400_16mb
t400_8mb
t400_4mb
t500_16mb
t500_8mb
t500_4mb
w500_16mb
w500_8mb
w500_4mb
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Moving the board-specific directories into projects/coreboot/configs/
and removing the payload-specific directories (depthcharge, seabios)
will allow for better management of Coreboot configs for each
board. Instead of having a config for each payload, there will be
at most two main configs (textmode, corebootfb) for each board.
Selecting a default payload will be reimplemented in a subsequent
commit.
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Patch based off:
https://review.coreboot.org/cgit/coreboot.git/commit/?id=92d483a8927066ef16603023be05ad1fb7dea644
by Jonathan Neuschäfer <j.neuschaefer@gmx.net>
|
|\ \ \
| |_|/
|/| | |
|
|/ / |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
I'm moving the website to another server which doesn't have much bandwidth, so
i can't host this mirror anymore. I have plenty of other backups, however, and
there are other mirrors.
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This script's purpose is to rotate the screen and/or Wacom stylus
and/or trackpoint orientation for more comfortable drawing and writing
on a touch screen. Requires `xrandr` and `xsetwacom` on the system.
Various desktop environments have different levels of automation, so
options `-s`, `-p`, `-t` determine whether to rotate the screen, pen
or trackpoint.
Only the main screen is rotated (LVDS1 or LVDS-1 depending on
kernel). Furthermore the input device rotations follow the main
screen.
_THERE MIGHT BE ISSUES WITH EXTERNAL MONITORS_ Check!
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \ |
|
| | | | |
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | | |
A very minor change, but bothered me a few times. So here it is.
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
into master
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
The URL fragments in the link did not match the anchor names on the
"Hardware" page.
|
|\ \ \ \
| |/ / /
|/| | | |
|
|/ / / |
|
|\ \ \ |
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
|
|/ / / |
|
|\ \ \ |
|