From picasawebalbums-noreply at google.com  Sun Jan  2 13:01:20 2011
From: picasawebalbums-noreply at google.com (Picasa Web Albums)
Date: Sun, 02 Jan 2011 18:01:20 +0000
Subject: =?GB2312?B?QjJCxOq0+tLRuf3IpaOs1ve2r7LF09DTxdbKv827pw==?=
Message-ID: <0016363b979aa0dbda0498e0d23c@google.com>

??11????????????180????????300????????
??????????????????????????????????
??????????
Q  Q?1754132144????????
???13556835687(???)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: @L_8WBMAWQTHZGM%(7NTP64.jpg
Type: image/jpeg
Size: 27359 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm/attachments/20110102/8726e42c/attachment-0001.jpg>

From picasawebalbums-noreply at google.com  Sun Jan  2 13:01:28 2011
From: picasawebalbums-noreply at google.com (Picasa Web Albums)
Date: Sun, 02 Jan 2011 18:01:28 +0000
Subject: =?GB2312?B?yOe6zsTcubu/qrei09DWysG/tcS/zbuno78=?=
Message-ID: <0016364c5d1518321b0498e0d3e6@google.com>

?????????????????????????????


???????????  ?????????????? ?????????? ? 
?????

??????1?????????????

??????2????B2B??"??"

??????3??????????????

??????4???????????

??????5????????????????

?????????????????????????wzl??????????? 
???????


????????????
????????????

?  ??13556835687  ? ??? wzl?

??? ??1754132144????????
-------------- next part --------------
A non-text attachment was scrubbed...
Name: @L_8WBMAWQTHZGM%(7NTP64.jpg
Type: image/jpeg
Size: 27359 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm/attachments/20110102/90103801/attachment-0001.jpg>

From picasawebalbums-noreply at google.com  Sun Jan  2 13:06:41 2011
From: picasawebalbums-noreply at google.com (Picasa Web Albums)
Date: Sun, 02 Jan 2011 18:06:41 +0000
Subject: =?GB2312?B?1rvT0LLO1bm1xMK3wvCjvw==?=
Message-ID: <0016364eecd292cbad0498e0d32b@google.com>

?????????????????????



??????????????

?????1000??????????????1000??????????????? 
???11????????170???????????????????????? 
??????????????????


Q Q:1754132144????????
Tel: 13556835687
???????
-------------- next part --------------
A non-text attachment was scrubbed...
Name: @L_8WBMAWQTHZGM%(7NTP64.jpg
Type: image/jpeg
Size: 27359 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm/attachments/20110102/c8b462f2/attachment-0001.jpg>

From remembering-chris-2011 at nsict.org  Sun Jan 16 10:00:40 2011
From: remembering-chris-2011 at nsict.org (remembering-chris-2011 at nsict.org)
Date: Sun, 16 Jan 2011 15:00:40 +0000 (GMT)
Subject: Chris Rutter, ten years on
Message-ID: <20110116150040.690999FCF@boyle.nsict.org>

Hi,

Some of you may remember Chris Rutter: he was active in ARM Linux
before his untimely death in March 2001.

This year is therefore the tenth anniversary of his death and some of
his friends intend to remember him in Cambridge, UK on the evening of
Tuesday March 1st.

The plan is to convene at 6pm outside the chapel in Clare College
(where he was a choral scholar) for evensong at 6:15pm. Afterwards,
we'll go to a restaurant for a meal and a chat. Anyone who wants to
join us would be most welcome.

So that we know numbers, please send an e-mail to this address
(remembering-chris-2011 at nsict.org) if you're thinking of coming. It
would be helpful if you included:
  - Your name, preferred e-mail address and mobile phone number.
  - Details of anyone else coming with you.
  - Any special notes, for example that can make the meal but not the
    service or vice-versa.
  - A plea for assistance if you don't know how to get to Clare
    College Chapel by your preferred mode of transport.

When we held a similar event five years ago there were a few people
who didn't find out about it until too late, so please forward this as
widely as possible to anyone who might be interested.

Thanks,

--Clive Jones.


From cshahnewaz at yahoo.com  Sun Jan  9 04:50:15 2011
From: cshahnewaz at yahoo.com (Shahnewaz Chowdhury)
Date: Sun, 09 Jan 2011 09:50:15 -0000
Subject: Untraceable problem with Minicom
Message-ID: <821611.77951.qm@web113702.mail.gq1.yahoo.com>

Dear all,

I am facing an untraceable problem with minicom. Allow me to provide proper 
details so that it will be easier to provide assistance.

I am using a desktop PC with Ubuntu 10.10. It has only one serial port (ttyS0) 
and I have verified that using the command " dmesg | grep tty ".

My development board is called HDP6410, which is a clone of the SMDK6410. The 
processor is S3C6410 with ARM 1176 JZ(F)-S core. After I start minicom, when I 
connect the board to the pc using a null-modem cable and power up the board I am 
supposed to see booting updates on minicom, followed by a prompt that would 
allow me to access the board. However, I do not see anything. I know that the 
serial port on the pc and the serial cable are fully functional because I do get 
all the booting updates and prompt when I use a custom serial communication 
software provided with the board. However, I want to use minicom because the 
custom software provides no means of transferring files.

I added my username to the following groups : dialout, uucp and tty.

I have also checked that ttyS0 has read/write permissions.

My settings in minicom are as follows:

Serial Device?????????????????????????? : /dev/ttyS0
Lockfile Location ??? ??? ??? ??? ??? : /var/lock
Bps / Par / Bits???????????????????????? : 115200 8N1
hardware flow control?? ??? ??? ??? : no
software flow control????????????????: no

I have tried running minicom both as?normal user and root, but I still get no 
output on the console when I power up the board. I know for sure that the serial 
port on the board is working fine and it does send messages once I power up the 
board. Something is wrong on the PC side. For some reason when I run minicom, 
the?connection is probably not established on the PC side.

Am I missing any essential configurations / settings ?

I would highly appreciated some guidance on this. I have been trying for a week 
now without any positive result. Please help.

Sincerely,
Shan


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm/attachments/20110109/1b149931/attachment.html>

From henryzhang62 at yahoo.com  Thu Jan 27 18:35:55 2011
From: henryzhang62 at yahoo.com (hong zhang)
Date: Thu, 27 Jan 2011 15:35:55 -0800 (PST)
Subject: mtd
Message-ID: <929718.13165.qm@web161702.mail.bf1.yahoo.com>

List,

On my TI board, default NAND MTD partition for file system is mtdblock7.
If SPI is not enabled, MTD partition has to be set to mtdblock3.

May I get this kind of information from MTD driver?

Thanks.

---henry  


      


From paulius.zaleckas at gmail.com  Fri Jan 28 03:11:39 2011
From: paulius.zaleckas at gmail.com (Paulius Zaleckas)
Date: Fri, 28 Jan 2011 10:11:39 +0200
Subject: mtd
In-Reply-To: <929718.13165.qm@web161702.mail.bf1.yahoo.com>
References: <929718.13165.qm@web161702.mail.bf1.yahoo.com>
Message-ID: <4D427A3B.9060101@gmail.com>

On 01/28/2011 01:35 AM, hong zhang wrote:
> List,
>
> On my TI board, default NAND MTD partition for file system is mtdblock7.
> If SPI is not enabled, MTD partition has to be set to mtdblock3.
>
> May I get this kind of information from MTD driver?

cat /proc/mtd
Is this what you are looking for?


From henryzhang62 at yahoo.com  Fri Jan 28 12:04:45 2011
From: henryzhang62 at yahoo.com (hong zhang)
Date: Fri, 28 Jan 2011 09:04:45 -0800 (PST)
Subject: mtd
In-Reply-To: <4D427A3B.9060101@gmail.com>
Message-ID: <928128.19880.qm@web161708.mail.bf1.yahoo.com>

Paul,

root at ti8168-evm:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00040000 00001000 "U-Boot"
mtd1: 00002000 00001000 "U-Boot Env"
mtd2: 00280000 00001000 "Kernel"
mtd3: 0013e000 00001000 "File System"
mtd4: 00260000 00020000 "U-Boot"
mtd5: 00020000 00020000 "U-Boot Env"
mtd6: 00440000 00020000 "Kernel"
mtd7: 0c820000 00020000 "File System"
mtd8: 03120000 00020000 "Reserved"

File System sits in mtd3 and mtd7. But only one of them can be used. In my case mtd7 is used when SPI is enabled or mtd3 is used w/o SPI. I do not know why.

---henry

--- On Fri, 1/28/11, Paulius Zaleckas <paulius.zaleckas at gmail.com> wrote:

> From: Paulius Zaleckas <paulius.zaleckas at gmail.com>
> Subject: Re: mtd
> To: "hong zhang" <henryzhang62 at yahoo.com>
> Cc: linux-arm at lists.infradead.org
> Date: Friday, January 28, 2011, 2:11 AM
> On 01/28/2011 01:35 AM, hong zhang
> wrote:
> > List,
> >
> > On my TI board, default NAND MTD partition for file
> system is mtdblock7.
> > If SPI is not enabled, MTD partition has to be set to
> mtdblock3.
> >
> > May I get this kind of information from MTD driver?
> 
> cat /proc/mtd
> Is this what you are looking for?
> 


      


From hartleys at visionengravers.com  Fri Jan 28 12:27:43 2011
From: hartleys at visionengravers.com (H Hartley Sweeten)
Date: Fri, 28 Jan 2011 11:27:43 -0600
Subject: mtd
In-Reply-To: <928128.19880.qm@web161708.mail.bf1.yahoo.com>
References: <4D427A3B.9060101@gmail.com>
	<928128.19880.qm@web161708.mail.bf1.yahoo.com>
Message-ID: <0D753D10438DA54287A00B027084269764CED92AE3@AUSP01VMBX24.collaborationhost.net>

On Friday, January 28, 2011 10:05 AM, hong zhang wrote:
>
> root at ti8168-evm:~# cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 00040000 00001000 "U-Boot"
> mtd1: 00002000 00001000 "U-Boot Env"
> mtd2: 00280000 00001000 "Kernel"
> mtd3: 0013e000 00001000 "File System"
> mtd4: 00260000 00020000 "U-Boot"
> mtd5: 00020000 00020000 "U-Boot Env"
> mtd6: 00440000 00020000 "Kernel"
> mtd7: 0c820000 00020000 "File System"
> mtd8: 03120000 00020000 "Reserved"
>
> File System sits in mtd3 and mtd7. But only one of them can be used. In
> my case mtd7 is used when SPI is enabled or mtd3 is used w/o SPI. I do
> not know why.

It looks like your spi device is getting processed by the mtd subsystem
before your actual flash device.  But both devices have the same partition
layout (and names) which is confusing you.

In the information shown above, mtd[0-3] all have an erasesize of 4KB.
These are probably associated with your spi device.  The remaining ones
all have an erasesize of 128KB so these are probably your flash device.

If you look are your boot messages you will probably be able to verify
this.  Look for something like: Creating <x> MTD partitions on "<name>".

The simplest solution would probably be changing the registration order
of the spi and flash devices in your platform init code.  That way the
flash partitions will always be first and the spi partitions, when enabled,
will come after.

Regards,
Hartley

From henryzhang62 at yahoo.com  Fri Jan 28 16:43:08 2011
From: henryzhang62 at yahoo.com (hong zhang)
Date: Fri, 28 Jan 2011 13:43:08 -0800 (PST)
Subject: mtd
In-Reply-To: <0D753D10438DA54287A00B027084269764CED92AE3@AUSP01VMBX24.collaborationhost.net>
Message-ID: <398500.30152.qm@web161719.mail.bf1.yahoo.com>

Paulius,

I check boot log and see exactly what say. I am going to exchange registration order and make NAND stays in mtdblock3 and SPI stays in mtdblock7 no matter SPI enabled or not.

Thanks.

----Henry

--- On Fri, 1/28/11, H Hartley Sweeten <hartleys at visionengravers.com> wrote:

> From: H Hartley Sweeten <hartleys at visionengravers.com>
> Subject: RE: mtd
> To: "hong zhang" <henryzhang62 at yahoo.com>, "Paulius Zaleckas" <paulius.zaleckas at gmail.com>
> Cc: "linux-arm at lists.infradead.org" <linux-arm at lists.infradead.org>
> Date: Friday, January 28, 2011, 11:27 AM
> On Friday, January 28, 2011 10:05 AM,
> hong zhang wrote:
> >
> > root at ti8168-evm:~# cat /proc/mtd
> > dev:? ?
> size???erasesize? name
> > mtd0: 00040000 00001000 "U-Boot"
> > mtd1: 00002000 00001000 "U-Boot Env"
> > mtd2: 00280000 00001000 "Kernel"
> > mtd3: 0013e000 00001000 "File System"
> > mtd4: 00260000 00020000 "U-Boot"
> > mtd5: 00020000 00020000 "U-Boot Env"
> > mtd6: 00440000 00020000 "Kernel"
> > mtd7: 0c820000 00020000 "File System"
> > mtd8: 03120000 00020000 "Reserved"
> >
> > File System sits in mtd3 and mtd7. But only one of
> them can be used. In
> > my case mtd7 is used when SPI is enabled or mtd3 is
> used w/o SPI. I do
> > not know why.
> 
> It looks like your spi device is getting processed by the
> mtd subsystem
> before your actual flash device.? But both devices
> have the same partition
> layout (and names) which is confusing you.
> 
> In the information shown above, mtd[0-3] all have an
> erasesize of 4KB.
> These are probably associated with your spi device.?
> The remaining ones
> all have an erasesize of 128KB so these are probably your
> flash device.
> 
> If you look are your boot messages you will probably be
> able to verify
> this.? Look for something like: Creating <x> MTD
> partitions on "<name>".
> 
> The simplest solution would probably be changing the
> registration order
> of the spi and flash devices in your platform init
> code.? That way the
> flash partitions will always be first and the spi
> partitions, when enabled,
> will come after.
> 
> Regards,
> Hartley




From henryzhang62 at yahoo.com  Fri Jan 28 17:36:38 2011
From: henryzhang62 at yahoo.com (hong zhang)
Date: Fri, 28 Jan 2011 14:36:38 -0800 (PST)
Subject: memory on ARM
Message-ID: <406434.65488.qm@web161719.mail.bf1.yahoo.com>

List,

My TI board has two memory ports at 0x80000000 and 0xC0000000. 1024Mbytes DDR2 connects at port 0x80000000 and nothing at 0xC000000. I assume Linux should not count any thing if 128M at 0xC000000 in kernel command line. 

Problems:

1. Boot log ignores 128M at 0xC000000, but total memory is Memory: "1102MB =  
   1102MB total NOT 1024M". 
2. Truncating RAM at 80000000-bfffffff to -afffffff (vmalloc region 
   overlap). It says it only gets 768M NOT 124M.

Any idea? See following boot log.

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37-rc3-24124-gde15396 (x0029463 at psplinux050) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Thu Dec0
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8168evm
vram size = 52428800 at 0
bootconsole [earlycon0] enabled
reserved size = 52428800 at 0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
Truncating RAM at 80000000-bfffffff to -afffffff (vmalloc region overlap).
Ignoring RAM at c0000000-c7ffffff (vmalloc region overlap).
OMAP chip is TI8168
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 195072
Kernel command line: console=ttyO2,115200n8 root=/dev/mtdblock7 rw rootfstype=jffs2 mem=1024M at 0x80000000 mem=128M at 0xC0000000
 vram=50M earlyprintk
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1102MB = 1102MB total
Memory: 774748k/774748k available, 11684k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xf0800000 - 0xf8000000   ( 120 MB)
    lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0035000   ( 180 kB)
      .text : 0xc0035000 - 0xc0428000   (4044 kB)
      .data : 0xc0428000 - 0xc0462c40   ( 236 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:400
GPMC revision 6.0

Thanks.

---Henry


      


From linux at arm.linux.org.uk  Fri Jan 28 18:08:38 2011
From: linux at arm.linux.org.uk (Russell King - ARM Linux)
Date: Fri, 28 Jan 2011 23:08:38 +0000
Subject: memory on ARM
In-Reply-To: <406434.65488.qm@web161719.mail.bf1.yahoo.com>
References: <406434.65488.qm@web161719.mail.bf1.yahoo.com>
Message-ID: <20110128230838.GB18376@n2100.arm.linux.org.uk>

On Fri, Jan 28, 2011 at 02:36:38PM -0800, hong zhang wrote:
> List,
> 
> My TI board has two memory ports at 0x80000000 and 0xC0000000.
> 1024Mbytes DDR2 connects at port 0x80000000 and nothing at 0xC000000.
> I assume Linux should not count any thing if 128M at 0xC000000 in kernel
> command line. 

Linux does not test the presence of memory.  That's the job of the boot
loader to report to the kernel where memory actually is.

If you tell it that there's memory present it will try to use it.  The
command line overrides what the boot loader tells the kernel because
it is assumed that whoever created the command line knows what they're
doing.

> Problems:
> 
> 1. Boot log ignores 128M at 0xC000000, but total memory is Memory: "1102MB =  
>    1102MB total NOT 1024M". 

That's because you've told it that there's 1024M + 128M, and it's claimed
50MB from that for VRAM.

> 2. Truncating RAM at 80000000-bfffffff to -afffffff (vmalloc region 
>    overlap). It says it only gets 768M NOT 124M.

Correct.  You can't fill memory completely as that leaves no space for
other purposes - such as mapping devices.  If you want to use that
additional memory you need to turn on highmem support.


From henryzhang62 at yahoo.com  Sat Jan 29 01:05:57 2011
From: henryzhang62 at yahoo.com (hong zhang)
Date: Fri, 28 Jan 2011 22:05:57 -0800 (PST)
Subject: memory on ARM
In-Reply-To: <20110128230838.GB18376@n2100.arm.linux.org.uk>
Message-ID: <32057.45431.qm@web161719.mail.bf1.yahoo.com>


> > 
> > My TI board has two memory ports at 0x80000000 and
> 0xC0000000.
> > 1024Mbytes DDR2 connects at port 0x80000000 and
> nothing at 0xC000000.
> > I assume Linux should not count any thing if
> 128M at 0xC000000 in kernel
> > command line. 
> 
> Linux does not test the presence of memory.? That's
> the job of the boot
> loader to report to the kernel where memory actually is.
> 
> If you tell it that there's memory present it will try to
> use it.? The
> command line overrides what the boot loader tells the
> kernel because
> it is assumed that whoever created the command line knows
> what they're
> doing.
> 
> > Problems:
> > 
> > 1. Boot log ignores 128M at 0xC000000, but total memory
> is Memory: "1102MB =? 
> >? ? 1102MB total NOT 1024M". 
> 
> That's because you've told it that there's 1024M + 128M,
> and it's claimed
> 50MB from that for VRAM.

But kernel says ignoring 128M at 0xC0000000. That means kernel knows physical memory 128M at 0xC0000000 is not presented and ignores it. Therefore, total memory should not count it. But it does.

> > 2. Truncating RAM at 80000000-bfffffff to -afffffff
> (vmalloc region 
> >? ? overlap). It says it only gets 768M NOT
> 124M.
> 
> Correct.? You can't fill memory completely as that
> leaves no space for
> other purposes - such as mapping devices.? If you want
> to use that
> additional memory you need to turn on highmem support.
> 




From eric.y.miao at gmail.com  Sat Jan 29 02:23:38 2011
From: eric.y.miao at gmail.com (Eric Miao)
Date: Sat, 29 Jan 2011 15:23:38 +0800
Subject: memory on ARM
In-Reply-To: <32057.45431.qm@web161719.mail.bf1.yahoo.com>
References: <20110128230838.GB18376@n2100.arm.linux.org.uk>
	<32057.45431.qm@web161719.mail.bf1.yahoo.com>
Message-ID: <AANLkTiku11FDp2qWi0t5HCDnvBL63+0PkbEtMdb1R-BF@mail.gmail.com>

On Saturday, January 29, 2011, hong zhang <henryzhang62 at yahoo.com> wrote:
>
>> >
>> > My TI board has two memory ports at 0x80000000 and
>> 0xC0000000.
>> > 1024Mbytes DDR2 connects at port 0x80000000 and
>> nothing at 0xC000000.
>> > I assume Linux should not count any thing if
>> 128M at 0xC000000 in kernel
>> > command line.
>>
>> Linux does not test the presence of memory.? That's
>> the job of the boot
>> loader to report to the kernel where memory actually is.
>>
>> If you tell it that there's memory present it will try to
>> use it.? The
>> command line overrides what the boot loader tells the
>> kernel because
>> it is assumed that whoever created the command line knows
>> what they're
>> doing.
>>
>> > Problems:
>> >
>> > 1. Boot log ignores 128M at 0xC000000, but total memory
>> is Memory: "1102MB =
>> >? ? 1102MB total NOT 1024M".
>>
>> That's because you've told it that there's 1024M + 128M,
>> and it's claimed
>> 50MB from that for VRAM.
>
> But kernel says ignoring 128M at 0xC0000000. That means kernel knows physical memory 128M at 0xC0000000 is not presented and ignores it. Therefore, total memory should not count it. But it does.
>

I guess that's because phys_to_virt() converted them beyond the
normal system ram mapping, and that overlaped with the vmalloc
region. But that part of memory, if is present, can be used in theory
if HIGHMEM is enabled.

>> > 2. Truncating RAM at 80000000-bfffffff to -afffffff
>> (vmalloc region
>> >? ? overlap). It says it only gets 768M NOT
>> 124M.
>>
>> Correct.? You can't fill memory completely as that
>> leaves no space for
>> other purposes - such as mapping devices.? If you want
>> to use that
>> additional memory you need to turn on highmem support.
>>
>
>
>
> _______________________________________________
> linux-arm mailing list
> linux-arm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm
>


From linux at arm.linux.org.uk  Sat Jan 29 04:42:22 2011
From: linux at arm.linux.org.uk (Russell King - ARM Linux)
Date: Sat, 29 Jan 2011 09:42:22 +0000
Subject: memory on ARM
In-Reply-To: <32057.45431.qm@web161719.mail.bf1.yahoo.com>
References: <20110128230838.GB18376@n2100.arm.linux.org.uk>
	<32057.45431.qm@web161719.mail.bf1.yahoo.com>
Message-ID: <20110129094222.GA28403@n2100.arm.linux.org.uk>

On Fri, Jan 28, 2011 at 10:05:57PM -0800, hong zhang wrote:
> > That's because you've told it that there's 1024M + 128M,
> > and it's claimed
> > 50MB from that for VRAM.
> 
> But kernel says ignoring 128M at 0xC0000000. That means kernel knows
> physical memory 128M at 0xC0000000 is not presented and ignores it.

No.  The kernel ignores it because it can't use it in the configuration
you've given.  It has precisely *nothing* to do with whether memory
is actually present or not.


From marek.vasut at gmail.com  Mon Jan 31 17:06:53 2011
From: marek.vasut at gmail.com (Marek Vasut)
Date: Mon, 31 Jan 2011 23:06:53 +0100
Subject: [PATCH] ARM: pxa: Properly configure PWM period for palm27x
Message-ID: <1296511613-24406-1-git-send-email-marek.vasut@gmail.com>

Signed-off-by: Marek Vasut <marek.vasut at gmail.com>
---
 arch/arm/mach-pxa/palm27x.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mach-pxa/palm27x.c b/arch/arm/mach-pxa/palm27x.c
index 7d1434a..4c9a938 100644
--- a/arch/arm/mach-pxa/palm27x.c
+++ b/arch/arm/mach-pxa/palm27x.c
@@ -322,7 +322,7 @@ static struct platform_pwm_backlight_data palm27x_backlight_data = {
 	.pwm_id		= 0,
 	.max_brightness	= 0xfe,
 	.dft_brightness	= 0x7e,
-	.pwm_period_ns	= 3500,
+	.pwm_period_ns	= 3500 * 1024,
 	.init		= palm27x_backlight_init,
 	.notify		= palm27x_backlight_notify,
 	.exit		= palm27x_backlight_exit,
-- 
1.7.2.3



From ulf.samuelsson at atmel.com  Mon Jan 31 17:58:40 2011
From: ulf.samuelsson at atmel.com (Ulf Samuelsson)
Date: Mon, 31 Jan 2011 23:58:40 +0100
Subject: Untraceable problem with Minicom
In-Reply-To: <821611.77951.qm@web113702.mail.gq1.yahoo.com>
References: <821611.77951.qm@web113702.mail.gq1.yahoo.com>
Message-ID: <4D473EA0.6000607@atmel.com>

Shahnewaz Chowdhury skrev:
> Dear all,
> 
> I am facing an untraceable problem with minicom. Allow me to provide proper 
> details so that it will be easier to provide assistance.
> 
> I am using a desktop PC with Ubuntu 10.10. It has only one serial port (ttyS0) 
> and I have verified that using the command " dmesg | grep tty ".
> 
> My development board is called HDP6410, which is a clone of the SMDK6410. The 
> processor is S3C6410 with ARM 1176 JZ(F)-S core. After I start minicom, when I 
> connect the board to the pc using a null-modem cable and power up the board I am 
> supposed to see booting updates on minicom, followed by a prompt that would 
> allow me to access the board. However, I do not see anything. I know that the 
> serial port on the pc and the serial cable are fully functional because I do get 
> all the booting updates and prompt when I use a custom serial communication 
> software provided with the board. However, I want to use minicom because the 
> custom software provides no means of transferring files.
> 
> I added my username to the following groups : dialout, uucp and tty.
> 
> I have also checked that ttyS0 has read/write permissions.
> 
> My settings in minicom are as follows:
> 
> Serial Device                           : /dev/ttyS0
> Lockfile Location                     : /var/lock
> Bps / Par / Bits                         : 115200 8N1
> hardware flow control               : no
> software flow control                : no
> 
> I have tried running minicom both as normal user and root, but I still get no 
> output on the console when I power up the board. I know for sure that the serial 
> port on the board is working fine and it does send messages once I power up the 
> board. Something is wrong on the PC side. For some reason when I run minicom, 
> the connection is probably not established on the PC side.
> 
> Am I missing any essential configurations / settings ?
> 
> I would highly appreciated some guidance on this. I have been trying for a week 
> now without any positive result. Please help.
> 
> Sincerely,
> Shan
> 
I would connect my host PC to another PC, and see if THAT works.

What does the modem init strings do you your board?
Are they cleared?

BR
Ulf Samuelsson
> 
>       
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> linux-arm mailing list
> linux-arm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm



