dev/ram" first and let me know if its
working.
Midhun.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
if its
working.
Midhun.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi All,
Sorry for crossposting.
> Let's see ... Linux-ARM is a "please don't crosspost" list;
I did not know that. I will not repeat. I did not know which list
to ask help for USB untill afterwards I found the linux-usb-users
mailing list. Sorry again. Will not repeat.
T
b = 0x0007 rootstat = 0x
portst1= 0x0100 portst2= 0x0103 portst3 = 0x0100
imx21_hc_hub_control:1579
GetPortStatus: port: 2, 0x100103
imx21_hc_hub_status_data:1555
port 1 (of 3): 0x100103
imx21_hc_hub_control:1579
ClearPortFeature
USB_PORT_FEA
ClearPortFeature
USB_PORT_FEAT_C_RESET
usb 1-2: device descriptor read/64, error -110
imx21_hc_hub_control:1579
ClearPortFeature
USB_PORT_FEAT_ENABLE
The host controller has been configured for Full speed only. Should
I change the speed to LOW?
Thanks,
Midhun.
-
To unsubscribe from
Hi All,
Sorry for crossposting.
Let's see ... Linux-ARM is a please don't crosspost list;
I did not know that. I will not repeat. I did not know which list
to ask help for USB untill afterwards I found the linux-usb-users
mailing list. Sorry again. Will not repeat.
Thanks,
Midhun
are not getting correct values for the touchscreen
positions. The SPI registers always return a value of 4096. We have
checked for correct clock. But still it does not help.
Has anybody faced a similar problem before?
Thanks,
Midhun.
-
To unsubscribe from this list: send the line "unsubscribe
are not getting correct values for the touchscreen
positions. The SPI registers always return a value of 4096. We have
checked for correct clock. But still it does not help.
Has anybody faced a similar problem before?
Thanks,
Midhun.
-
To unsubscribe from this list: send the line unsubscribe linux
. :(
Thanks anyways,
Midhun.
On 7/30/07, Alan Cox <[EMAIL PROTECTED]> wrote:
> On Mon, 30 Jul 2007 11:20:58 +0530
> "Sriram, Kannan" <[EMAIL PROTECTED]> wrote:
>
> >
> > Midhun,
> >
> > There is no open-source implementation of CPRM (SD-A
. :(
Thanks anyways,
Midhun.
On 7/30/07, Alan Cox [EMAIL PROTECTED] wrote:
On Mon, 30 Jul 2007 11:20:58 +0530
Sriram, Kannan [EMAIL PROTECTED] wrote:
Midhun,
There is no open-source implementation of CPRM (SD-Audio/ SD-Bind
standards). So first of all, you need to license keys from 4C
by the 4C Entity) and test our prototype. But I could find
none. There are IP cores but no manufactured chips.
Has anybody of you done similar stuff ? How do I go about testing
the CPRM feature of the SD card on our prototype ?
Thanks,
Midhun.
-
To unsubscribe from this list: send the line
by the 4C Entity) and test our prototype. But I could find
none. There are IP cores but no manufactured chips.
Has anybody of you done similar stuff ? How do I go about testing
the CPRM feature of the SD card on our prototype ?
Thanks,
Midhun.
-
To unsubscribe from this list: send the line unsubscribe
rm_device imx_mmc_device.
Is it necessary that the firmware (may be bootloader) notify about
the MMC host to Linux? The kernel documentation (platform.txt) says :
"The firmware should notify the platform bus about devices before the
legacy drivers have had a chance to load."
Have I
be bootloader) notify about
the MMC host to Linux? The kernel documentation (platform.txt) says :
The firmware should notify the platform bus about devices before the
legacy drivers have had a chance to load.
Have I interpreted the above sentence correctly?
Thanks,
Midhun.
-
To unsubscribe from
-mmc.0: RESP 0x, 0x, 0x,
0x, error 1
<7>MMC: req done (37): 1:
<7>MMC: starting cmd 37 arg flags 0015
<7>imx-mmc imx-mmc.0: CMD55 (0x37) mask set to 0x003b
<7>imx-mmc imx-mmc.0: CMD TIMEOUT
<7>
platform_driver_register() method. What is the
difference between the two?
Thanks,
Midhun.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FA
platform_driver_register() method. What is the
difference between the two?
Thanks,
Midhun.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
.0: clock 0 power 0 vdd 0 width 1
Thanks,
Midhun.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
what can be done with this driver.
Thanks a lot for all the help.
Thanks,
Midhun.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FA
Not likely. It's probably a no-op when you don't have devfs.
CONFIG_MMC_DEBUG is already enabled. This is not printing any debug
statements as such.
Midhun.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
This uses the function devfs_mk_dir() - defined in
linux/fs/devfs/base.c. I don't have devfs enabled in my kernel (kernel
version 2.6.16. In fact I don't even get an option to enable it in
menuconfig.). Can this be the cause of the problem?? I have found the
same code in the original kernel ver
drwxr-xr-x2 00 0 Jan 1 00:00 ram7
drwxr-xr-x2 00 0 Jan 1 00:00 ram8
drwxr-xr-x2 00 0 Jan 1 00:00 ram9
Midhun.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
mtd
128 ptm
136 pts
Block devices:
1 ramdisk
1 ramdisk
31 mtdblock
254 mmc
So is the major number 254 is correct for MMC ??
Midhun.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
oblem.
The kernel version is 2.6.16. So I guess there should not be a
problem. Any more things that I need to check??
Thanks,
Midhun.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.
-
customized for CSB535FS board. I want to try udev only as my last
option.
Please help me resolve this issue. I have been on it for a week now.
Thanks a lot,
Midhun.
The dmesg log:
<7>jffs2_add_physical_node_ref(): Node at 0x160300(2), size 0x124
<7>jffs2_write_dnod
-
customized for CSB535FS board. I want to try udev only as my last
option.
Please help me resolve this issue. I have been on it for a week now.
Thanks a lot,
Midhun.
The dmesg log:
7jffs2_add_physical_node_ref(): Node at 0x160300(2), size 0x124
7jffs2_write_dnode wrote node at 0x00160300
guess there should not be a
problem. Any more things that I need to check??
Thanks,
Midhun.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
mtd
128 ptm
136 pts
Block devices:
1 ramdisk
1 ramdisk
31 mtdblock
254 mmc
So is the major number 254 is correct for MMC ??
Midhun.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
drwxr-xr-x2 00 0 Jan 1 00:00 ram7
drwxr-xr-x2 00 0 Jan 1 00:00 ram8
drwxr-xr-x2 00 0 Jan 1 00:00 ram9
Midhun.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
/fs/devfs/base.c. I don't have devfs enabled in my kernel (kernel
version 2.6.16. In fact I don't even get an option to enable it in
menuconfig.). Can this be the cause of the problem?? I have found the
same code in the original kernel version too (the one from
kernel.org).
Thanks,
Midhun
Not likely. It's probably a no-op when you don't have devfs.
CONFIG_MMC_DEBUG is already enabled. This is not printing any debug
statements as such.
Midhun.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
what can be done with this driver.
Thanks a lot for all the help.
Thanks,
Midhun.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
-----
From: Midhun Agnihotram <[EMAIL PROTECTED]>
Date: Jun 28, 2007 10:30 PM
Subject: Fwd: Mounting MMC card
To: linux-kernel@vger.kernel.org
Cc: [EMAIL PROTECTED]
Hi All,
I am new to linux kernel stuff. I am using Cogent CSB535FS board. I
have configured the kernel to include supp
, mmcblk0p1,etc. But of no use. How
do I access the contents of MMC card? Is there any thing missing in my
settings? Busybox does not say anything other than the above error
message.
Any clue will be appreciated,
Thanks,
Midhun.
-
To unsubscribe from this list: send the line "unsubscribe linux-k
, mmcblk0p1,etc. But of no use. How
do I access the contents of MMC card? Is there any thing missing in my
settings? Busybox does not say anything other than the above error
message.
Any clue will be appreciated,
Thanks,
Midhun.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
: Midhun Agnihotram [EMAIL PROTECTED]
Date: Jun 28, 2007 10:30 PM
Subject: Fwd: Mounting MMC card
To: linux-kernel@vger.kernel.org
Cc: [EMAIL PROTECTED]
Hi All,
I am new to linux kernel stuff. I am using Cogent CSB535FS board. I
have configured the kernel to include support for MMC card and also
36 matches
Mail list logo
