From: ruben@mrbrklyn.com (Ruben Safir)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Get Back Into Kernel Work
Date: Sun, 15 Mar 2015 11:48:57 -0400 [thread overview]
Message-ID: <5505A9E9.6000009@mrbrklyn.com> (raw)
In-Reply-To: <20150315125521.GA2193@levex-pc.home.ilevex.eu>
On 03/15/2015 08:55 AM, Levente Kurusa wrote:
> Hello, Nick.
>
> On Sun, Mar 15, 2015 at 12:34:33AM -0400, nick wrote:
>> Greetings All,
>> After my terrible results before and getting banned from the list due to these results,
>> I am wondering if there is any work in the USB or Networking Subsystem I can start with.
>> Further more recently I read Essential Kernel Drivers so I have some idea of how
>> to write drivers now and want to get my feet wet. In addition if I am still not
>> trusted yet,that's OK too. :)
>
> Well, ideally what you should do is look through drivers/staging and
> select a driver that looks interesting to you and has some work that
> needs to be done, then you get a hardware for that particular driver.
> Please do not skip the step where you actually get the hardware, given
> your previous behavior I think we all can agree that is likely to happen
> though... Surprise us! ;-) If you have the hardware, you can run tests
> on it, stress test it or boot into Windows and see what the Windows
> driver does that the current Linux driver does not do.
>
> Hopefully the hardware itself won't cost too much and is easily obtainable
> using Amazon or Ebay.
>
> Hope it helps,
> Levente
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
Did this get hijacked?
next prev parent reply other threads:[~2015-03-15 15:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 4:34 Get Back Into Kernel Work nick
2015-03-15 9:07 ` Robert P. J. Day
2015-03-15 12:28 ` Nicholas Krause
2015-03-15 12:55 ` Levente Kurusa
2015-03-15 15:48 ` Ruben Safir [this message]
2015-03-15 16:01 ` Nicholas Krause
2015-03-15 16:14 ` Sudip Mukherjee
2015-03-15 16:16 ` Nicholas Krause
2015-03-15 16:16 ` Levente Kurusa
2015-03-15 16:24 ` Ruben Safir
2015-03-15 16:39 ` Hugo Mills
2015-03-15 16:46 ` Ruben Safir
2015-03-16 3:05 ` nick
2015-03-15 17:16 ` Nicholas Krause
2015-03-23 13:51 ` el_es
2015-03-23 15:04 ` Nicholas Krause
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=5505A9E9.6000009@mrbrklyn.com \
--to=ruben@mrbrklyn.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 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 NNTP newsgroup(s).