lla wrote:
> >
> >
> > On 19/11/2020 12:43, David Brown wrote:
> >> I'm not aware of anyone working on it. It might be worthwhile to at
> least create a github issue for it (there is one for RISC-V). The code
> generator in Chez is fairly custom, but there are a
I'm not aware of anyone working on it. It might be worthwhile to at least
create a github issue for it (there is one for RISC-V). The code generator
in Chez is fairly custom, but there are a lot of similarities between
aarch32 and aarch64, so it would be a relatively easier port.
Porting Chez to a
On Fri, Feb 19, 2016 at 02:32:40PM +, Daniel Lezcano wrote:
From: Daniel Lezcano
Did you mean to have these patches authored by your @free.fr address,
but sent from Linaro?
Subject: Re: [PATCH 1/6] Change options to flag approach.
You might want to put something in to state what repo
On Mon, May 27, 2013 at 08:02:44PM +0530, Sanjay Singh Rawat wrote:
use cpu_do_idle for entering the wfi mode.
Signed-off-by: Sanjay Singh Rawat
---
arch/arm/mach-msm/hotplug.c |9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
Acked-by: David Brown
--
sent by an employee of
On Mon, May 27, 2013 at 08:02:44PM +0530, Sanjay Singh Rawat wrote:
> use cpu_do_idle for entering the wfi mode.
>
> Signed-off-by: Sanjay Singh Rawat
> ---
> arch/arm/mach-msm/hotplug.c |9 ++---
> 1 file changed, 2 insertions(+), 7 deletions(-)
Acked-by: David Brow
Christopher Covington writes:
> On 04/17/2013 06:29 AM, Jon Medhurst (Tixy) wrote:
>> On Wed, 2013-04-17 at 06:21 +0200, Jonathan Aquilina wrote:
>>> Doesnt email run the risk of a patch slipping through the cracks?
>>
>> And with gerrit the patch author needs to get an account enabled with the
On Tue, Jun 12, 2012 at 02:47:31PM +, Arnd Bergmann wrote:
> Ok, thank you very much!
>
> This confirms that it is the same as my 8 GB essential card, and I would
> not recommend using this kind of card in production systems with an ext4
> or similar file system.
>
> From what I can tell, al
On Fri, Jun 08, 2012 at 02:06:55AM +, Arnd Bergmann wrote:
> On Thursday 07 June 2012, David Brown wrote:
> > On Wed, Jun 06, 2012 at 07:11:37AM +, Arnd Bergmann wrote:
> >
> > > If you don't need the data on your card, could you run these
> > > comm
On Wed, Jun 06, 2012 at 07:11:37AM +, Arnd Bergmann wrote:
> If you don't need the data on your card, could you run these
> commands on yours:
>
> for i in 2 3 30 31 ; do
> sudo flashbench --open-au --open-au-nr=30 --erasesize=$[512 * 1024] \
> /dev/mmcblk0 --offset=$[24
On Mon, Jun 04, 2012 at 03:36:55PM +, Arnd Bergmann wrote:
> I can always need more samples. If anyone has Samsung cards at hand, could you
> send the output of "tail -n 100 /sys/block/mmcblk0/device/* /proc/partitions"?
I'm not exactly sure what these are. It says "Samsung 16GB Class 10,
an
On Fri, Nov 18, 2011 at 04:47:17PM +0530, Rajendra Nayak wrote:
> + xyzreg: regulator@0 {
> + regulator-min-microvolt = <100>;
> + regulator-max-microvolt = <250>;
> + regulator-always-on;
> + vin-supply = <&vin>;
> + };
Just noticed
On Mon, Feb 13, 2012 at 10:07:17AM -0600, Tom Gall wrote:
> From what I've heard and saw it seemed like the google+ hangouts in
> the rooms worked fairly well. (For the very small sample size of the
> people I've talked to)
My experience wasn't so good. I think the issue may have been
resolved,
On Tue, Dec 20, 2011 at 07:16:56PM +, Jon Medhurst (Tixy) wrote:
> On Tue, 2011-12-20 at 12:45 -0600, Xianghua Xiao wrote:
> > where does it mandate 3G/1G in Android?
> >
> > we're planning to use 2G/2G split as well, but I'm unaware of the
> > 3G/1G requirement in Android, seems odd to me.
>
On Sat, Nov 05, 2011 at 05:30:22PM +0530, Sandeep Sharma wrote:
> I was migrating changes from GB(K 2.6.35) to K 3.0 but every time my
> PMEM allocation in board file leads to crash the kernel before
> serial up. Now I am taking CAF kernel as reference but the change
> in MACHINE_START structure(
On Thu, Sep 01, 2011 at 10:40:27AM +0100, Andrew Stubbs wrote:
> I'm currently trying to get GCC to auto-detect what CPU to optimize
> for by finding out what CPU it's actually running on (the user would
> only have to pass -mcpu=native). It does this simply by reading
> /proc/cpuinfo.
>
> The pr
On Thu, Aug 25, 2011 at 12:12:59PM +0200, Linus Walleij wrote:
> mach-msm:
>
>
> Hard to tell how this works and what's available, support
> seems to be incomplete. Currently it seems to be wired
> to do either a dedicated function (like some UART pin)
> or GPIO, like each pin ca
16 matches
Mail list logo
