From: Felix Janda <felix.janda@posteo.de>
To: musl@lists.openwall.com
Subject: Re: sys/io.h lacks inb_p and outb_p on x86
Date: Tue, 10 Nov 2015 09:50:52 +0100 [thread overview]
Message-ID: <20151110085052.GA332@nyan> (raw)
In-Reply-To: <20151110150818.5820b37d@r2lynx>
Рысь wrote:
[..]
>
> So, after three+ years of experience with musl I just hit this once,
> and I don't think they worth adding if there is no much interest.
>
> memtest86+ uses no libc code, and suddenly only grabs those two from
> host which is easily patchable.
It also has an "io.h" which should define inb_p and outb_p via some
"misuse" of macros. Can't it use that instead of <sys/io.h>?
Felix
next prev parent reply other threads:[~2015-11-10 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 4:26 Рысь
2015-11-08 4:50 ` Rich Felker
2015-11-08 5:13 ` Рысь
2015-11-08 5:23 ` Rich Felker
2015-11-09 22:17 ` Rich Felker
2015-11-10 8:08 ` Рысь
2015-11-10 8:50 ` Felix Janda [this message]
2015-11-10 9:29 ` Рысь
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=20151110085052.GA332@nyan \
--to=felix.janda@posteo.de \
--cc=musl@lists.openwall.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).