From: Sean MacLennan <smaclennan@pikatech.com>
To: "Grzegorz Bernacki" <gjb@semihalf.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Add support for the digsy MTC board.
Date: Mon, 2 Feb 2009 11:11:01 -0500 [thread overview]
Message-ID: <20090202111101.5f95bd8b@lappy.seanm.ca> (raw)
In-Reply-To: <4986EC33.9000600@semihalf.com>
On Mon, 02 Feb 2009 13:50:59 +0100
"Grzegorz Bernacki" <gjb@semihalf.com> wrote:
> I would like to have support for following devices in defconfig for
> digsy:
> - LXT PHY
> - RTC DS1337
> - EEPROM AT24
> - MTD partitioning based on OF description
I am seeing a problem where if I enable CONFIG_EEPROM_LEGACY and
CONFIG_EEPROM_AT24, then the at24 driver does not work. Would you mind
trying that?
> BTW,
> I noticed that there are some problems with mounting file system
> over NFS on Linux-2.6.29-rc3, I see following messages:
> ...
> [ 339.813807] nfs: server 192.168.1.1 not responding, still trying
> [ 339.832144] nfs: server 192.168.1.1 OK
> ...
>
> I haven't noticed in on Linux-2.6.29-rc2. Is there any known problem?
Does it only happen at mount time? We get this quite often at work,
but it never happens at home. I assumed it was just due to the flaky
networking at work.
Cheers,
Sean
next prev parent reply other threads:[~2009-02-02 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 15:33 [PATCH] Add support for the digsy MTC board Grzegorz Bernacki
2009-01-30 16:59 ` Grant Likely
2009-02-02 12:50 ` Grzegorz Bernacki
2009-02-02 15:00 ` Grant Likely
2009-02-02 16:11 ` Sean MacLennan [this message]
2009-02-02 16:44 ` Grzegorz Bernacki
2009-02-02 16:52 ` Sean MacLennan
2009-02-02 16:17 ` Andre Schwarz
2009-02-02 16:42 ` Grzegorz Bernacki
2009-02-02 23:58 ` Wolfgang Denk
2009-02-03 0:05 ` Grant Likely
2009-02-03 8:04 ` Grzegorz Bernacki
2009-02-03 11:08 ` Andre Schwarz
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=20090202111101.5f95bd8b@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=gjb@semihalf.com \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).