public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] What is the difference between /lib and /common
Date: Wed, 01 Jun 2011 22:03:32 +0200	[thread overview]
Message-ID: <20110601200332.F167ACEFB4E@gemini.denx.de> (raw)
In-Reply-To: <4DE0D3C2.50004@gmail.com>

Dear Graeme Russ,

In message <4DE0D3C2.50004@gmail.com> you wrote:
> 
> A quick question for you - What defines what belongs in /lib versus /common?

/lib should be stuff that is called from (several, many) other files,
while /common is architecture independent code like the central main
loop, command handlers, etc.

> I get that cmd* and env* belong in /common (U-Boot specific) and crc, zlib,
> gunzip, qsort etc belong in /lib (generic)

Correct.

> But others are a bit grey like malloc in /common and display_options() in /lib

s/grey/wrong/

> The reason I ask is to know where to put the new timer API - I'm thinking
> /lib/time.c with udelay() makes the most sense

Agreed.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
God made machine language; all the rest is the work of man.

      parent reply	other threads:[~2011-06-01 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-28 10:51 [U-Boot] What is the difference between /lib and /common Graeme Russ
2011-05-28 14:53 ` Mike Frysinger
2011-06-01 20:03 ` Wolfgang Denk [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=20110601200332.F167ACEFB4E@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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