archives of rust-dev@mozilla.org (2010-2015)
 help / color / mirror / Atom feed
* [rust-dev] Kernel Rust
@ 2014-12-17 16:02 Kevin McGuire
  2014-12-17 17:22 ` Kevin McGuire
  0 siblings, 1 reply; 3+ messages in thread
From: Kevin McGuire @ 2014-12-17 16:02 UTC (permalink / raw)
  To: rust-dev

[-- Attachment #1: Type: text/plain, Size: 853 bytes --]

I saw your post about your rust kernel. Did you ever figure out what was
wrong?

Also have you tried using QEMU?

First I would verify that your serial code is actually running. You could
triple fault the x86_64 to detect if it reaches a certain point.

Also setup of serial port on QEMU for x86_64 is very easy. All you do is
send the data and check the buffer. I have some great example Rust code.
Now real hardware is different because it can be touchy if you dont
properly intialize it.

Your code looks good okay so im wondering if it can be verified as running
- like I said QEMU can help you diagnose simple problems thsy will be
present in real hardware. Also be aware of QEMU monitor mode which lets you
dump the CPU registers during runtime so you can see exactly what the CPU
is executing.

Let me know because I can likely help you a bunch.

[-- Attachment #2: Type: text/html, Size: 896 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [rust-dev] Kernel Rust
  2014-12-17 16:02 [rust-dev] Kernel Rust Kevin McGuire
@ 2014-12-17 17:22 ` Kevin McGuire
  2014-12-18  7:48   ` C K Kashyap
  0 siblings, 1 reply; 3+ messages in thread
From: Kevin McGuire @ 2014-12-17 17:22 UTC (permalink / raw)
  To: rust-dev

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

Well, actually I notice your code does not check that the UART buffer is
full which I think it is supposed to check, however from your mail it seems
like it is not outputting anything?

On Wed, Dec 17, 2014 at 10:02 AM, Kevin McGuire <kmcg3413@gmail.com> wrote:
>
> I saw your post about your rust kernel. Did you ever figure out what was
> wrong?
>
> Also have you tried using QEMU?
>
> First I would verify that your serial code is actually running. You could
> triple fault the x86_64 to detect if it reaches a certain point.
>
> Also setup of serial port on QEMU for x86_64 is very easy. All you do is
> send the data and check the buffer. I have some great example Rust code.
> Now real hardware is different because it can be touchy if you dont
> properly intialize it.
>
> Your code looks good okay so im wondering if it can be verified as running
> - like I said QEMU can help you diagnose simple problems thsy will be
> present in real hardware. Also be aware of QEMU monitor mode which lets you
> dump the CPU registers during runtime so you can see exactly what the CPU
> is executing.
>
> Let me know because I can likely help you a bunch.
>

[-- Attachment #2: Type: text/html, Size: 1448 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [rust-dev] Kernel Rust
  2014-12-17 17:22 ` Kevin McGuire
@ 2014-12-18  7:48   ` C K Kashyap
  0 siblings, 0 replies; 3+ messages in thread
From: C K Kashyap @ 2014-12-18  7:48 UTC (permalink / raw)
  To: Kevin McGuire; +Cc: rust-dev

[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]

Thanks Kevin,

I need all the help - thanks for offering.
Regarding the &str issue - it went away after I replaced the linker script
with the one from osdev.org.

I've run into a new issue (link issue - I've sent an email about it) with
the latest nightly - something may have broken in the latest nightly

Regards,
Kashyap

On Wed, Dec 17, 2014 at 10:52 PM, Kevin McGuire <kmcg3413@gmail.com> wrote:
>
> Well, actually I notice your code does not check that the UART buffer is
> full which I think it is supposed to check, however from your mail it seems
> like it is not outputting anything?
>
> On Wed, Dec 17, 2014 at 10:02 AM, Kevin McGuire <kmcg3413@gmail.com>
> wrote:
>>
>> I saw your post about your rust kernel. Did you ever figure out what was
>> wrong?
>>
>> Also have you tried using QEMU?
>>
>> First I would verify that your serial code is actually running. You could
>> triple fault the x86_64 to detect if it reaches a certain point.
>>
>> Also setup of serial port on QEMU for x86_64 is very easy. All you do is
>> send the data and check the buffer. I have some great example Rust code.
>> Now real hardware is different because it can be touchy if you dont
>> properly intialize it.
>>
>> Your code looks good okay so im wondering if it can be verified as
>> running - like I said QEMU can help you diagnose simple problems thsy will
>> be present in real hardware. Also be aware of QEMU monitor mode which lets
>> you dump the CPU registers during runtime so you can see exactly what the
>> CPU is executing.
>>
>> Let me know because I can likely help you a bunch.
>>
>
> _______________________________________________
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
>

[-- Attachment #2: Type: text/html, Size: 2595 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-12-18  7:49 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-17 16:02 [rust-dev] Kernel Rust Kevin McGuire
2014-12-17 17:22 ` Kevin McGuire
2014-12-18  7:48   ` C K Kashyap

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox