From: Nicolas DET <nd@bplan-gmbh•de>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, tnt@246tNt•com, sl@bplan-gmbh•de
Subject: Re: [PATCH] General CHRP/MPC5K2 Platform and drivers support - to comment
Date: Fri, 20 Oct 2006 16:24:11 +0200 [thread overview]
Message-ID: <4538DC0B.7060402@bplan-gmbh.de> (raw)
In-Reply-To: <122A4E06-B8A6-4256-B96E-3811EA93EA25@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
Kumar Gala wrote:
>>
>> > 4. look at replacing sram_allocator w/rheap
>> >
>>
>> This SRAM allocator is the exact same from the original Linux one. In
>> fact, it is the original one. Would it be possible to accept this code
>> as it is and schedule rheap integration later ?
>
> I dont follow, what do you mean by 'original Linux one' ?
There are already some kind of Bestcomm DMA engine supoprt for some
embbeded system (ARCH=ppc). In order to speed up the developement, the
API is (almost) compatible so we can use the drivers wrote for this API.
For example, the Ethernet driver enterily rely on this API. However, the
'soon to be release' ATA driver has been rewritten.
I did not at the time (yet) to look at rheap, but I know the current
allocator is not really good (it can not free!).
I was just thinking, as this code is alraedy in some Linux tree, we
could still use it there, and plan to replace it by a much better one
(keeping the API compatible) later on.
Regards,
[-- Attachment #2: nd.vcf --]
[-- Type: text/x-vcard, Size: 249 bytes --]
begin:vcard
fn:Nicolas DET ( bplan GmbH )
n:DET;Nicolas
org:bplan GmbH
adr:;;;;;;Germany
email;internet:nd@bplan-gmbh•de
title:Software Entwicklung
tel;work:+49 6171 9187 - 31
x-mozilla-html:FALSE
url:http://www.bplan-gmbh.de
version:2.1
end:vcard
next prev parent reply other threads:[~2006-10-20 14:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 12:39 [PATCH] General CHRP/MPC5K2 Platform and drivers support - to comment Nicolas DET
2006-10-19 14:12 ` Jon Loeliger
2006-10-19 16:18 ` Linas Vepstas
2006-10-19 16:26 ` Grant Likely
2006-10-19 23:41 ` Benjamin Herrenschmidt
2006-10-20 5:55 ` Kumar Gala
2006-10-19 17:43 ` Olof Johansson
2006-10-20 6:06 ` Kumar Gala
2006-10-20 6:29 ` Sven Luther
2006-10-20 6:29 ` Benjamin Herrenschmidt
2006-10-20 8:12 ` Nicolas DET
2006-10-20 14:18 ` Kumar Gala
2006-10-20 14:24 ` Nicolas DET [this message]
2006-10-20 14:34 ` Kumar Gala
2006-10-21 23:25 ` Benjamin Herrenschmidt
2006-10-22 12:56 ` Nicolas DET
2006-10-23 6:36 ` Benjamin Herrenschmidt
2006-10-23 14:47 ` Matt Sealey
2006-10-23 15:52 ` Christoph Hellwig
2006-10-23 16:25 ` Matt Sealey
2006-10-23 16:40 ` Segher Boessenkool
2006-10-23 21:38 ` Benjamin Herrenschmidt
2006-10-23 22:57 ` Paul Mackerras
2006-10-24 15:44 ` Matt Sealey
2006-10-24 16:01 ` Becky Bruce
2006-10-24 23:01 ` Paul Mackerras
2006-10-25 14:44 ` Matt Sealey
2006-10-25 14:50 ` Kumar Gala
2006-10-25 14:56 ` Matt Sealey
2006-10-25 14:57 ` Grant Likely
2006-10-25 16:18 ` Matt Sealey
2006-10-25 17:08 ` Olof Johansson
2006-10-25 21:29 ` Paul Mackerras
2006-10-25 21:22 ` Paul Mackerras
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=4538DC0B.7060402@bplan-gmbh.de \
--to=nd@bplan-gmbh$(echo .)de \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=sl@bplan-gmbh$(echo .)de \
--cc=tnt@246tNt$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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