From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] processor specific drivers: drivers/ or cpu/$proc/ ?
Date: Mon, 1 Oct 2007 14:33:19 +0200 [thread overview]
Message-ID: <200710011433.19890.sr@denx.de> (raw)
In-Reply-To: <200710010804.16985.vapier@gentoo.org>
Mike,
On Monday 01 October 2007, Mike Frysinger wrote:
> another area of inconsistency ... if i have a driver for an on-chip
> peripheral, should it live in the cpu/$proc/ tree or driver/ tree ? for
> example, a driver for the UART or TWI or MAC ...
Plan is to move all those drivers into drivers/xxx/yyy. So a uart driver for
example should live in
drivers/serial/
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2007-10-01 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 12:04 [U-Boot-Users] processor specific drivers: drivers/ or cpu/$proc/ ? Mike Frysinger
2007-10-01 12:33 ` Stefan Roese [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=200710011433.19890.sr@denx.de \
--to=sr@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