public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephan Linz <linz@mazet.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH-1/2] LAN91C111
Date: Tue, 4 Nov 2003 19:45:25 +0100	[thread overview]
Message-ID: <0311041945250S.02205@pcj86> (raw)
In-Reply-To: <71555548814716479478431542AA5F8A058D28@dlee2k98.ent.ti.com>


Hi,

I'm just back to NIOS.

Am Montag,  3. November 2003 19:04 schrieb Woodruff, Richard:
> As to the 8bit to 16 access change, at both the boot and kernel I use 16
> bit accesses.  I'm ok using 8bit access on my board, but based on comments
> in code and the ifdef's in the shipping kernel code, switching that access
> size will break a few boards.  As word access works, I wouldn't switch that
> bit.

Oops, very interesting informations, because the SMSC's manuals for LAN91C110 
and LAN91C1111 sayes about SMC91111_INT_REG: "... This register can be read 
and write as a word or two individual bytes ...". So I'm wondering about a 
few boards will be broken.

Nevertheless, let's leave it at 16bit access. The NIOS board is running in 
both cases, so there is no really important reason to change this bit.

>
> As far as testing goes, if it works on my board I'm usually happy.  My
> opinion would be if you are submitting new code, it doesn't really matter
> if it works for anyone else as long as it doesn't break the compile.  If
> its existing code, then some more care is obviously necessary.

Yes of course, the 16bit to 8 change isn't really important. I've thought it 
could be a good minor code generalization. It wasn't my intention to make 
broken code.

So, here my second try. In attachment yo will find the patch again without 
this critical change.

>
> From a group submission aspect, Wolfgang does a good job of filtering and
> moderating, and likely applies similar logic for submission.  He is
> probably is a bit more stringent in certain areas as the code would become
> more difficult to maintain with out some control.

Oh yes, he does a good job for us.


Regards,
Stephan


> > From: wd at denx.de [mailto:wd at denx.de]
> > Sent: Monday, November 03, 2003 9:40 AM
> > To: Stephan Linz
> > Cc: Woodruff, Richard; u-boot-users at lists.sourceforge.net
> > Subject: Re: [U-Boot-Users] [PATCH-1/2] LAN91C111
> >
> >
> > Dear Stephan,
> >
> > in message <0311031553480Q.02205@pcj86> you wrote:
> > > I'm curious about it. When your test phase / cross check
> > --8<--snipp-->8--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: u-boot-20031103cvs-smc91111_fix.patch-0
Type: text/x-c
Size: 2320 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20031104/d96e77c7/attachment.bin 

  reply	other threads:[~2003-11-04 18:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 18:04 [U-Boot-Users] [PATCH-1/2] LAN91C111 Woodruff, Richard
2003-11-04 18:45 ` Stephan Linz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-04 19:08 Woodruff, Richard
2003-11-03 13:06 Woodruff, Richard
2003-11-03 14:53 ` Stephan Linz
2003-11-03 15:40   ` Wolfgang Denk
2003-11-03 12:13 Woodruff, Richard
2003-11-03 13:01 ` Stephan Linz
2003-11-03 11:02 Stephan Linz
2003-12-06 23:16 ` Wolfgang Denk

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=0311041945250S.02205@pcj86 \
    --to=linz@mazet.de \
    --cc=u-boot@lists.denx.de \
    /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