From: Derek Johansen <djohanse678@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Memory issues and USB support?
Date: Sun, 19 Mar 2017 00:02:20 -0600 [thread overview]
Message-ID: <CAOv0vdk52GC6wS0Nb-g2_Uge3Fg6KNtRsfcSiAwEGNzOzXeXwA@mail.gmail.com> (raw)
Just out of curiosity:
1) Why the restriction to ~640K of memory for running ELKS. Lots of
implementations banging up against this lately. Can ELKS be modified
to use all available memory (e,g, my virtual system has ~1 GB
available; could ELKS be modified to use all of that)?
2) Does ELKS support USB devices? Will it ever? Is it even possible?
Thanks,
Derek
next reply other threads:[~2017-03-19 6:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 6:02 Derek Johansen [this message]
2017-03-19 13:57 ` Memory issues and USB support? Jody Bruchon
2017-03-19 14:27 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2017-06-04 13:55 David O'Shea
2017-06-05 14:41 ` Alan Cox
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=CAOv0vdk52GC6wS0Nb-g2_Uge3Fg6KNtRsfcSiAwEGNzOzXeXwA@mail.gmail.com \
--to=djohanse678@gmail.com \
--cc=linux-8086@vger.kernel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).