From: Edoardo Liverani <eddyx89@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Development in progress
Date: Sat, 26 Apr 2014 20:19:54 +0200 [thread overview]
Message-ID: <CALNwxewawF+20qB_2Zga9LFdyskN+onwe2DOxuu0Au24hjboiQ@mail.gmail.com> (raw)
In-Reply-To: <CA+E3k90gaSUt5PLNCVABCpCDatoWTD1yY8Thz4SdNCc9Nxa9zQ@mail.gmail.com>
Hi Jody,
I'm following your great job.
Out of curiosity, about dev86, are you going to try to remove the 64k
limit from bcc or just adjusting something here and there?
On Sat, Apr 26, 2014 at 6:26 PM, Royce Williams <royce@tycho.org> wrote:
> Jody, that's excellent! It really seems like a high-leverage
> activity. I look forward to helping with testing.
>
> Royce
>
> On Sat, Apr 26, 2014 at 8:21 AM, Jody Bruchon <jody@jodybruchon.com> wrote:
>> I wanted to let the list know that I have been working on ELKS recently and
>> I have also forked and begun some additional work on dev86. My number one
>> goal right now is to develop a system that will allow rapid construction of
>> bootable disk images to build and test ELKS on modern systems and emulators
>> such as QEMU.
>>
>> My work is at https://github.com/jbruchon?tab=repositories
>>
>> -Jody Bruchon
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-04-26 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 16:21 Development in progress Jody Bruchon
2014-04-26 16:26 ` Royce Williams
2014-04-26 18:19 ` Edoardo Liverani [this message]
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=CALNwxewawF+20qB_2Zga9LFdyskN+onwe2DOxuu0Au24hjboiQ@mail.gmail.com \
--to=eddyx89@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).