From: Petr Tesarik <ptesarik@suse.cz> To: Linux console tools development discussion <kbd@lists.altlinux.org> Subject: Re: [kbd] [PATCH v2] setleds: add option to reset state to the BIOS default Date: Mon, 30 Jul 2012 19:27:11 +0200 Message-ID: <201207301927.11868.ptesarik@suse.cz> (raw) In-Reply-To: <5015A6BB.5030507@gmail.com> Hi Alexey, glad you didn't smash the idea from an ideological standpoint. Dne Ne 29. července 2012 23:10:19 Alexey Gladkov napsal(a): > 27.07.2012 11:09, Petr Tesarik wrote: > > +#if defined(__i386__) || defined(__x86_64__) > > +# define HAVE_BIOS 1 > > I think it's strange condition. It is, indeed. For one thing, some Itanium machines also have the standard PC BIOS Data Area (BDA), and they don't get this new feature. Unfortunately, some (early?) SGI Altix machines don't have physical memory at 0x400, and they don't handle accesses to non-existent RAM very well (read: freeze or reboot). OTOH detecting the machine model and maintaining a blacklist or whitelist of well-known IA-64 systems in setleds sounds like overkill, especially for a dying platform. So, I didn't include them. > How your code will work on the EFI ? Well, UEFI will work just fine, same with Intel's EFI, because they include a Compatibility Support Module (CSM), which (among other things) initializes legacy BDA. Yes, some machines don't do that properly (IIRC Phoenix issued an errata a few years ago exactly to fix LED states in the BDA). Even Apple includes a CSM for their EFI implementation... I would be a bit more concerned about embedded hardware like the one I used to have in one of my ancient D-Link routers in the early 2000's, which emulated an x86 on top of ICplus Corp. IC175. However, platforms like this usually run in a well-controlled environment, so the firmware writer will probably not even attemp to use this new setleds feature. In any case, even if the BDA is not initialized properly, the worst thing that happens is that the LEDs are set incorrectly when you run "setleds bios". Petr Tesarik SUSE Linux
next prev parent reply other threads:[~2012-07-30 17:27 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-27 7:09 Petr Tesarik 2012-07-29 21:10 ` Alexey Gladkov 2012-07-30 17:27 ` Petr Tesarik [this message] 2012-08-02 20:36 ` Alexey Gladkov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=201207301927.11868.ptesarik@suse.cz \ --to=ptesarik@suse.cz \ --cc=kbd@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Linux console tools development discussion This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/kbd/0 kbd/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 kbd kbd/ http://lore.altlinux.org/kbd \ kbd@lists.altlinux.org kbd@lists.altlinux.ru kbd@lists.altlinux.com public-inbox-index kbd Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.kbd AGPL code for this site: git clone https://public-inbox.org/public-inbox.git