All of lore.kernel.org
 help / color / mirror / Atom feed
From: philipp.muhoray@gmail.com (Philipp Muhoray)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Choosing the right environment
Date: Tue, 18 Nov 2014 17:24:53 +0100	[thread overview]
Message-ID: <546B72D5.9060900@gmail.com> (raw)
In-Reply-To: <48803.1416325011@turing-police.cc.vt.edu>


Am 2014-11-18 um 16:36 schrieb Valdis.Kletnieks at vt.edu:
> On Tue, 18 Nov 2014 20:54:05 +0530, somebody said:
>>> - I could go with a virtual machine on one of my main machines ??? But I'm not
>>> quite sure whether the hardware-abstraction will give me troubles when
>>> hacking on hardware drivers (which I want to start with)
> If you're hacking at hardware drivers, you *hopefully* have the hardware
> to test with.  At that point, the *biggest* question is "What does that
> hardware plug into?".   If it's a USB device, you have lots of options for
> the host hardware.  If it's a PCI card, you need a system that has PCI
> slots.  If you're hacking on the Raspberri Pi camera driver, you're kind of
> going to need a Pi.  And so on....

Actually I wanted to hack on hardware I don't have so that you guys 
could test it, but your idea seems good as well. Just kidding, of course 
I'll check first what HW I have laying around; then I play with it.
By now I'm developing in VirtualBox, doing the Eudyptula challenge. I 
think it's the most convenient option so far.

And thanks for answering me. I almost thought my question was too 
stupid/naive to be answered.

      reply	other threads:[~2014-11-18 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 13:12 sched_clock generic for all architectures Hemanth Kumar
2014-11-01 14:41 ` Choosing the right environment Philipp Muhoray
2014-11-18 15:03   ` Gusman Dharma Putra
2014-11-18 15:24     ` Saket Sinha
2014-11-18 15:36       ` Valdis.Kletnieks at vt.edu
2014-11-18 16:24         ` Philipp Muhoray [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=546B72D5.9060900@gmail.com \
    --to=philipp.muhoray@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.