On Wed, May 21, 2008 at 11:42:04AM +0530, Madhusudhan Chikkature Rajashekar
wrote:
After the end of the I/O errors I can umount the partition that was
mounted and I reinsert the card.
That's rather expected - outstanding IO has to be errored when the
medium is removed.
It seem not to work
-Original Message-
From: Russell King - ARM Linux [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 21, 2008 1:00 PM
To: Madhusudhan Chikkature Rajashekar
Cc: 'Pierre Ossman'; linux-omap@vger.kernel.org;
[EMAIL PROTECTED]
Subject: Re: MMC/SD cards hotplug scenario
On Wed, May
Hello,
How do i enable UART2 on omap5912_osk in the kernel?
and is there a way by which i can test if the uart2 has been recongnised?
i dont see uart module being initialized during the kernel boot-up.
thank you.
regards,
Shareef
--
To unsubscribe from this list: send the line unsubscribe
Hi,
Please use the vger list.
It seems like you are getting DTO on CMD53.
One thing you might want to check is did the card configuration path went fine
before you issue CMD53.
Before your card driver issues CMD53, I guess the SDIO core issues a series of
CMD52 to read the card capabilities
On Wednesday 21 May 2008 15:48:27 you wrote:
the SDIO core issues a series of CMD52 to read the card capabilities and
Setup the bus width etc... Does these go through fine for the card you are
using? Does the core detect the new SDIO card?
Yes, all these go fine and the core detects a new
* mohammed shareef [EMAIL PROTECTED] [080520 23:43]:
Hello,
How do i enable UART2 on omap5912_osk in the kernel?
and is there a way by which i can test if the uart2 has been recongnised?
i dont see uart module being initialized during the kernel boot-up.
You need to enable it in
* Bryan Wu [EMAIL PROTECTED] [080519 01:06]:
On Mon, May 19, 2008 at 3:49 PM, Felipe Balbi [EMAIL PROTECTED] wrote:
On Mon, 19 May 2008 14:39:10 +0800, Bryan Wu [EMAIL PROTECTED] wrote:
On Sat, May 17, 2008 at 10:37 PM, David Brownell [EMAIL PROTECTED]
wrote:
On Saturday 17 May 2008,
* Kamat, Nishant [EMAIL PROTECTED] [080519 02:50]:
Tony,
From: Tony Lindgren [mailto:[EMAIL PROTECTED]
* Nishant Kamat [EMAIL PROTECTED] [080515 07:45]:
+#define DEBUG_BASE 0x0800
+
+#define OMAP34XX_ETHR_START DEBUG_BASE
+#define LDP_SMC911X_CS
On Wednesday 21 May 2008, Tony Lindgren wrote:
Great, after I enable the DMA mode 1 on Blackfin and cleanup the code,
I will send
out the code before you sent them to upstream
Maybe we should get the musb code to USB tree before that? It's been out
of the scope for linux-omap tree for
Each bit enables one uart.
For uarts 1, 2, 3 it will look like:
static struct omap_uart_config osk_uart_config __initdata = {
.enabled_uarts = (1 0) | (1 1) | (1 2),
};
Just a hint. You can look board-xxx.c config files and see examples
there.
Roman Tereshonkov
-Original
* mohammed shareef [EMAIL PROTECTED] [080521 10:12]:
i see the following lines in the omap-osk.c file regarding the uarts:
static struct omap_uart_config osk_uart_config __initdata = {
.enabled_uarts = (1 0),
};
what does it mean? i want all my uarts (1,2,3) enabled. how do i
On Wed, 21 May 2008 15:01:00 +0530
Madhusudhan Chikkature Rajashekar [EMAIL PROTECTED] wrote:
What I meant here is that reinsertion of the card does not seem to result in
reinitialization of the card consistently.
Previously, that has always been because of bad interactions with the
block
Hi Tony,
On Wed, 21 May 2008, Tony Lindgren wrote:
* Paul Walmsley [EMAIL PROTECTED] [080520 18:20]:
Modify mach-omap2/irq.c to simplify the IRQ number-to-IRQ register and IRQ
number-to-register bit calculations.
How about patching Jouni's new omap_irq_pending() for this too?
done -
On Wed, 21 May 2008 10:44:28 -0700, Tony Lindgren [EMAIL PROTECTED] wrote:
* mohammed shareef [EMAIL PROTECTED] [080521 10:12]:
i see the following lines in the omap-osk.c file regarding the uarts:
static struct omap_uart_config osk_uart_config __initdata = {
.enabled_uarts = (1 0),
On Wednesday 21 May 2008, Felipe Balbi wrote:
I'm all for getting the musb_hdrc driver into the 2.6.27 queue...
I presume there are still some infrastructure changes in usbcore
that block that merge? It'd be nice if we could merge musb_hdrc
without those changes (OTG related) and then
On Wed, May 21, 2008 at 4:04 PM, David Brownell wrote:
That said, I'm looking forward to seeing the www.beagleboard.org
hardware [1] become more generally available. That will make some
musb_hdrc hardware available in a more developer-friendly rig than,
say, an N810 tablet. And it might well
* Felipe Balbi [EMAIL PROTECTED] [080521 12:37]:
On Wed, 21 May 2008 10:44:28 -0700, Tony Lindgren [EMAIL PROTECTED] wrote:
* mohammed shareef [EMAIL PROTECTED] [080521 10:12]:
i see the following lines in the omap-osk.c file regarding the uarts:
static struct omap_uart_config
On Thu, 22 May 2008 03:46:37 +0530, mohammed shareef
[EMAIL PROTECTED] wrote:
when i type:
ls -l /dev/ttyS0
crw-rw-rw-1 root root 4, 64 Aug 8 2004
\0x1b[1;35m/dev/ttyS0\0x1b[0m
# ls -l /dev/ttyS1
-rw-r--
...
that's a bit weird. What does cat /proc/tty/drivers show ?
# cat /proc/tty/drivers
/dev/tty /dev/tty5 0 system:/dev/tty
/dev/console /dev/console5 1 system:console
/dev/ptmx/dev/ptmx 5 2 system
/dev/vc/0/dev/vc/0 4 0 system:vtmaster
serial /dev/ttyS
On Thu, 22 May 2008 04:01:17 +0530, mohammed shareef
[EMAIL PROTECTED] wrote:
# cat /proc/tty/drivers
/dev/tty /dev/tty5 0 system:/dev/tty
/dev/console /dev/console5 1 system:console
/dev/ptmx/dev/ptmx 5 2 system
/dev/vc/0
Hello,
i have enabled the SPI and ADS7846 drivers during kernel (2.6.18)
compilation. i could see in the kernel boot log that they are also
initialized.
ads7846 spi2.0: touchscreen + hwmon, irq 164
input: ADS784x
Hi all,
Turns out my recent DMA changes broke omap1 dma to some extent.
I've pushed a fix for that, and also a fix for old alsa code,
and a compile fix for H4.
I also fixed omap_get_dma_src/dst_pos() to return the current
address. So if there are still some old drivers (wrongly) assuming
this
22 matches
Mail list logo
