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 <[email protected]> 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 <[email protected]> > 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 > [email protected] > https://mail.mozilla.org/listinfo/rust-dev > >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
