Re: [GIT PATCH] more Driver core patches for 2.6.19

Hi!

> > Well.. it is easier to debug in userspace. While bad hw access can
> > still kill the box, bad free() will not, and most bugs in early
> > developent are actually of 2nd kind.
> 
> Isn't that what qemu is for?

I do not think you can reasonably debug driver for new hardware under
qemu.

Anyway, doing it in userspace is just convenient.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [GIT PATCH] more Driver core patches for 2.6.19
    • From: Greg KH <[email protected]>
  • Re: [GIT PATCH] more Driver core patches for 2.6.19
    • From: Linus Torvalds <[email protected]>
  • Re: [GIT PATCH] more Driver core patches for 2.6.19
    • From: "Michael K. Edwards" <[email protected]>
  • Re: [GIT PATCH] more Driver core patches for 2.6.19
    • From: Linus Torvalds <[email protected]>
  • Re: [GIT PATCH] more Driver core patches for 2.6.19
    • From: Pavel Machek <[email protected]>
  • Re: [GIT PATCH] more Driver core patches for 2.6.19
    • From: Jörn Engel <[email protected]>

• Prev by Date: RE: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19]
• Next by Date: error: 'struct work_struct' has no member named 'management'
• Previous by thread: Re: [GIT PATCH] more Driver core patches for 2.6.19
• Next by thread: Re: [GIT PATCH] more Driver core patches for 2.6.19
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]