LKML Archive on
help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <>
To: Greg KH <>
Cc: Muni Sekhar <>,
	Oliver Neukum <>,
	kernelnewbies <>,,
Subject: LDD 3rd ed. - It was: Re: read() via USB bus
Date: Thu, 12 Aug 2021 11:45:45 +0200	[thread overview]
Message-ID: <13470108.apdoE9Qb8s@localhost.localdomain> (raw)
In-Reply-To: <YRDq530N/>

Hi Greg,

On Monday, August 9, 2021 10:44:23 AM CEST Greg KH wrote:
> On Mon, Aug 09, 2021 at 10:15:29AM +0200, Oliver Neukum wrote:
> > On 09.08.21 09:58, Muni Sekhar wrote:
> > > Hi all,
> > > 
> > > PCIe memory mapped registers can be read via readb(), readw(), readl()
> > > kernel API's. Similarly what are the kernel API to read the device
> > > registers via USB bus
> > 
> > [...]
> >
> > I hope this list stays friendly to newcomers and we will answer
> > specific questions, but at this point I must advise you to first
> > read an introductory book.
> Along these lines, take a look at the book, Linux Device Drivers, third
> edition, which is free online, as it has a chapter about USB drivers and
> how they work.  That should help you out to understand the issues
> involved with USB devices.
I've heard that your book, LDD 3rd edition, has become obsolete a long time 
ago and most sample code cannot anymore build. Reading what you wrote above 
seems to contradict what I've been told by others... I must admit that I've 
just had a print copy of it that I have not yet opened for reading, therefore 
maybe that I'm totally wrong in assuming the above.

Do you mind to elaborate a bit more on this subject, please? I mean: can you 
point out which chapters, which content, should be skipped (if there's really 
something which is no more correct/relevant to today's practice of drivers  
development and kernel hacking?

One more question, please... if after carefully studying its content, someone 
wanted to change and update part of the book content to reflect the changes in 
Linux API and in the current best practices, would it be (legally) allowed to 
publish a v4 on GitHub for the convenience of everyone interested in learning 
for free? However, I understand that it would be not so easy to come up with a 
good and error free text if not addressed as a public long term project and 
I'm also not sure of what tools are needed to edit PDF files. (At the moment 
my question is for a hypothetical scenario, just to know whether or not it 
would be technically and legally doable). 

I suppose that the answers to the above questions might be of interest to a 
lot of newcomers like me, so please, if you have time, I'd appreciate to read 
your reply.


> If you have specific questions after looking at that, and reading the
> basic usb-skeleton.c driver in the kernel source tree, please let us
> know!
> thanks,
> greg k-h

  reply	other threads:[~2021-08-12  9:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09  7:58 Muni Sekhar
2021-08-09  8:15 ` Oliver Neukum
2021-08-09  8:44   ` Greg KH
2021-08-12  9:45     ` Fabio M. De Francesco [this message]
2021-08-12 10:13       ` LDD 3rd ed. - It was: " Valdis Klētnieks
2021-08-12 10:18       ` Greg KH
2021-08-12 10:26         ` Robert P. J. Day
2021-08-09 16:19   ` Muni Sekhar
2021-08-10 14:13   ` Muni Sekhar
2021-08-10 14:20     ` Oliver Neukum
     [not found]       ` <>
2021-08-11 10:04         ` Oliver Neukum

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13470108.apdoE9Qb8s@localhost.localdomain \ \ \ \ \ \ \ \
    --subject='LDD 3rd ed. - It was: Re: read() via USB bus' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).