From: Alex Dubov <oakad@yahoo.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, drzeus-list@drzeus.cx,
rmk+lkml@arm.linux.org.uk
Subject: Re: [PATCH 1/2] [MMC] Driver for TI FlashMedia card reader - source
Date: Wed, 20 Sep 2006 19:51:06 -0700 (PDT) [thread overview]
Message-ID: <20060921025106.61978.qmail@web36707.mail.mud.yahoo.com> (raw)
In-Reply-To: <20060919232016.68a02e0e.akpm@osdl.org>
> Could I ask where the information which permitted this (nice-looking) driver to
> be written came from?
I had 3 sources for this:
1. win64 binary driver
2. linux binary driver - it says its license is GPL, but source is nowhere to be found
3. OMAP 5912 datasheet for part of the tifm_sd functionality
My upcoming memorystick driver only draws from the first two sources. I should also add that I
never worked for TI nor Everest Consulting (the authors of the binary driver) and don't know
anybody who ever did.
> The driver has lots of really big inlined functions. It's best to uninline
> these. If the function has a single callsite, gcc will inline it anyway.
> If the function has multiple callsites (now, or in the future), inlining it
> is undesirable.
I actually marked them "inline" to signify the fact that only one callsite is intended for these
functions. They are not intended to be called from arbitrary places (no problem to fix those,
though).
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-09-21 2:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 6:02 Alex Dubov
2006-09-20 6:20 ` Andrew Morton
2006-09-20 6:28 ` Pekka Enberg
2006-09-20 16:36 ` Dave Jones
2006-09-21 5:15 ` Alexey Dobriyan
2006-09-21 2:51 ` Alex Dubov [this message]
2006-09-22 6:24 ` [PATCH 1/2 try 2] " Alex Dubov
2006-09-20 6:22 ` [PATCH 1/2] " Pierre Ossman
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=20060921025106.61978.qmail@web36707.mail.mud.yahoo.com \
--to=oakad@yahoo.com \
--cc=akpm@osdl.org \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®