public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: jana1972@centrum.cz, linux-media@vger.kernel.org
Subject: Re: Developers blogs
Date: Sun, 26 Jan 2014 17:55:05 +0200	[thread overview]
Message-ID: <52E52FD9.2060706@iki.fi> (raw)
In-Reply-To: <52DF9A9A.14029.1F9A8A4A@jana1972.centrum.cz>

Hi Jahn

On 22.01.2014 11:16, Jahn wrote:
>   Hi everyone,
> I am a newbie in V4L fields so I
>    search for various info about V4L to study available details
>   I am happy I found few blogs that provides
>   interesting  information
>   e.g.
>   http://blog.palosaari.fi/

=) My plan has been share some hardware level information, mostly from 
consumer market USB DTV devices, as those are the devices I am familiar. 
Give some general info how these sticks are are build on a level chips 
are interconnected, from the driver developer point of view. One thing 
what I have tried to tell is how to gather needed information using some 
common reverse-engineering techniques, needed by about every Linux 
developer working with these devices.

One thing I would like to do is demodulator reverse-engineering 
tutorial. Unfortunately I haven't found suitable example yet, as it 
should be some DVB USB device having existing drivers for USB interface 
and RF tuner, and simple USB protocol. EC100/EC168 is one very good 
example, but unfortunately I have done its driver ages back. Maybe I 
should rewrite it from the scratch :)


>   http://www.kernellabs.com/blog/?page_id=2066

Especially I like to read those articles related of sniffing hardware 
directly from the bus (I2C, IF, ...).

>
>   but if I found even more ....
>
>
> I think it would be a good idea  if anyone
>   in the vger.kernel.org list could provide his blog's ( website) address
>   so that we can share knowledge   together.
>   What do you think?


regards
Antti

-- 
http://palosaari.fi/

      parent reply	other threads:[~2014-01-26 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22  9:16 Developers blogs Jahn
2014-01-22 14:21 ` Steven Toth
2014-01-26 15:55 ` Antti Palosaari [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=52E52FD9.2060706@iki.fi \
    --to=crope@iki.fi \
    --cc=jana1972@centrum.cz \
    --cc=linux-media@vger.kernel.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