LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Muni Sekhar <munisekharrms@gmail.com>,
	Oliver Neukum <oneukum@suse.com>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: LDD 3rd ed. - It was: Re: read() via USB bus
Date: Thu, 12 Aug 2021 12:18:55 +0200	[thread overview]
Message-ID: <YRT1j20SRYXpPsXc@kroah.com> (raw)
In-Reply-To: <13470108.apdoE9Qb8s@localhost.localdomain>

On Thu, Aug 12, 2021 at 11:45:45AM +0200, Fabio M. De Francesco wrote:
> 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.

Look into it and see the differences, it's not hard to notice.

And the code samples are all up to date online on github somewhere,
there's people keeping them alive if you want to track them down, but
really, just look at the in-kernel drivers for better examples of real
drivers.

> 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?

I am not going to create a study guide like this, sorry, I've already
given away the book for free to you :)

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

Please see the license of the book for what you are, and are not,
allowed to do with it to answer this question.

thanks,

greg k-h

  parent reply	other threads:[~2021-08-12 10:19 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     ` LDD 3rd ed. - It was: " Fabio M. De Francesco
2021-08-12 10:13       ` Valdis Klētnieks
2021-08-12 10:18       ` Greg KH [this message]
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]       ` <CAHhAz+ioThu3v4VW6LVqFn9MhgNaqv=qDoxh8Orkw2LOEC_JYA@mail.gmail.com>
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:
  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=YRT1j20SRYXpPsXc@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=fmdefrancesco@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=munisekharrms@gmail.com \
    --cc=oneukum@suse.com \
    --subject='Re: LDD 3rd ed. - It was: Re: read() via USB bus' \
    /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

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