On Tue, Apr 29, 2014 at 11:36 AM, ron minnich <rminnich(a)gmail.com> wrote:
> Anybody out there know typical numbers for the timer tick if USB is
> active as part of SMM?
> I just heard one number for one product line, 8 HZ. We're seeing a
> mysterious 18 HZ tick on one system. Any other numbers people know?
18.2 Hz is legacy stuff,
http://wiki.osdev.org/Programmable_Interval_Timer- but the particulars
of an SMM implementation might just as well be a
copy-paste error, for all I know.
An OHCI driver might use a timer tick to recover after a timeout. The USB
spec doesn't specify all the timeouts, though multiples of 100ms are common
(so a ~10HZ timer might be useful).
Hope that helps,
Anybody out there know typical numbers for the timer tick if USB is
active as part of SMM?
I just heard one number for one product line, 8 HZ. We're seeing a
mysterious 18 HZ tick on one system. Any other numbers people know?
Amd Parmer and Olivehill support FAN control. EC is used in these boards to
control fan speed.
On Sat, Apr 12, 2014 at 9:04 AM, Vitor Augusto <vitorafsr(a)gmail.com> wrote:
> I'm searching for any information about where (memory, IO port, etc.)
> the status (on or off) of the fans of a laptop are stored. Anything is
> very welcome! This is to improve the compatibility of i8kutils package
> at Linux. The site of the development is
> Thanks in advance.
> Vitor Augusto
> coreboot mailing list: coreboot(a)coreboot.org
I'm new to coreboot, and I'm working to use it with an ASROCK IMB-A180,
the H version with the LVDS port.
I've read previous posts regarding the "IMB-A180 won't boot" on this group,
and tried the .config that was posted, but the result is the same.
The debugging output shows things progressing until agesawwrapper_amdinitmid
is called, then the boot restarts, then stops cold at the same point:
Done allocating resources.
BS: BS_DEV_RESOURCES times (us): entry 0 run 1095130 exit 0
Fam16 - domain_enable_resources: AmdInitMid.
^@^@^@^@§H¨Hh½É<95><89>½½Ñµ4.0-5169-g9d1d740 Tue Feb 4 16:46:38 PST
Any help with this would be greatly appreciated. Full serial debug
output then .config are attached below.
Engineering Design Team
As you may know ReactOS is now working in the new ReactOS Community Edition.
It's a new OS, with new features, redesigned image, powered by the new ReactOS kernel which boosts its compatibility with apps and drivers. You can see a comparative, and the new site here: http://community.reactos.org/index.php/features/reactos-0-4
In the spirit of open source we created a special "Open Source Support Program" available only for open source projects.
And, of course, absolutely free.
Its main objective is to promote your app and show the users that there are "other" alternatives out there and apps waiting to be discovered!
But not only that, there are other nice features that you shouldn't miss, because they are free after all.
We've (literally) chained a designer into a dark wet basement for a week to create some designs which explain not just the "Opensource Support Program", but also the "Official Software Support" program, which you can join for free too.
Make him happy by watching his artwork! http://community.reactos.org/programs/opensource.pdf
We hope you will like and consider joining any of these new programs.
Since we're planning ahead, we had to set some deadlines in the doc. Don't miss the date!
Any comments, suggestions and enhancements are really appreciated so we can expand the features and make them even better.
Also we're crowdfunding right now to make ReactOS Community Edition happen ASAP, so any help in spreading the word is most welcome!
Thank you for reading and for "reacting" to the email ;)
Disclaimer: No designer was harmed in the making of the attached document. He is recovering well! ;)
Víctor Martínez Calvo (EN/ES/DE/FR)
Programs & Partnerships Coordinator
Sorry for the late reply.
Tue Apr 15 08:42:36 CEST 2014, Paul :
> The problem is probably that you have `USE_OPTION_TABLE` selected, where
> the default is to restart on powerloss.
The default option is "# CONFIG_USE_OPTION_TABLE is not set". I
activated this option "CONFIG_USE_OPTION_TABLE=y" and I encounter no
problems since :)
Thanks you very much, best regards
Dear coreboot folks,
in #coreboot on <irc.freenode.net> Stefan mentioned that link time
optimization (LTO)  might yield some speed improvements for coreboot
as the resulting firmware image might be smaller and therefore it takes
less time to read it from flash.
As LTO has been greatly improved in GCC 4.9.0 and is all over the news,
has somebody already experimented with LTO or created patches or tools
Is somebody able to share conclusions already? That’d be very
(search for `lto`)
if i try to build the cross gcc (make crossgcc) make tells me to use the
coreboot tool chain.
This behavior seems to be a result of comit 9b0de . With "allow other
i can build crossgcc. I assume the toolchain check needs to be disabled
for cross gcc or only enabled for coreboot itself and payloads.
On Mon, Apr 21, 2014 at 8:55 AM, David Hubbard <
> Agree 100%. On a slightly related note, the touchpad identifies itself as
>> "SynPS/2 Synaptics Touchpad," though I'm not 100% sure it's a synaptics
It depends which Chromebook you are using, as there are a variety of
touchpads used from Synaptics, Cypress, Atmel, etc. Also, make sure the
chromeos_laptop kernel module is loaded.
As Ron pointed out, this is really not an appropriate forum to get help on
touchpad issues. I suggest chromium-os-discuss mailing list for that:
> I foundnd the mouse moved ever so slightly when I touched or released the
> pad -- so I changed the expected finger size:
> xinput | grep 'SynPS/2' # to get the device id, should be 11
> xinput list-props 11
> # change "Synaptics Finger (271)"
> xinput --set-prop 11 37 42 0 # 37=min size of a finger, 42=max size of a
> # the previous value was: xinput --set-prop 11 25 30 0
> coreboot mailing list: coreboot(a)coreboot.org
David Hendricks (dhendrix)
Systems Software Engineer, Google Inc.