From: "Alok Singh" <alok.singh@broadcom.com>
To: "ariga masahiro" <ariga@link-lab.co.jp>,
"Gary Thomas" <gary@mlbassoc.com>,
"Andrew Lunn" <andrew@lunn.ch>
Cc: ecos-discuss@ecos.sourceware.org
Subject: RE: [ECOS] Can't Connect,TCP CHECKSUM INCORRECT
Date: Thu, 08 Nov 2007 09:13:00 -0000 [thread overview]
Message-ID: <E06E3B7BBC07864CADE892DAF1EB0FBD01FE1345@NT-SJCA-0752.brcm.ad.broadcom.com> (raw)
In-Reply-To: <002101c821aa$8ea9d1b0$1c0110ac@ariga>
Ariga,
Can you send your generated ecc file?
-Alok
-----Original Message-----
From: ariga masahiro [mailto:ariga@link-lab.co.jp]
Sent: Thursday, November 08, 2007 7:26 AM
To: Gary Thomas; Alok Singh; Andrew Lunn
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Can't Connect,TCP CHECKSUM INCORRECT
Hello,
Alok,thank you very much for your reply.
Alok wrote
> It will better if you remove all your little/big endian hacks. Or Take
a
> fresh view. And take care of the following -
I checked two parameters you suggest,but I was encountered next
questions
for each.
Please allow my ignorance and teach me how to settle it.
About,
> 1) CYGPKG_HAL_MIPS_MSBFIRST - should be defined, (and not
> CYGPKG_HAL_MIPS_LSBFIRST)
My target uses SH7709S.
CYGPKG_HAL_MIPS_MSBFIRST is included next cdl files,
packages\hal\mips\idt32334\current\cdl\hal_mips_idt32334.cdl(68):
cdl_option CYGPKG_HAL_MIPS_MSBFIRST {
packages\hal\mips\mips32\current\cdl\hal_mips_mips32.cdl(96):
cdl_option
CYGPKG_HAL_MIPS_MSBFIRST {
packages\hal\mips\rm7000\var\current\cdl\hal_mips_rm7000.cdl(118):
cdl_option CYGPKG_HAL_MIPS_MSBFIRST {
packages\hal\mips\tx39\current\cdl\hal_mips_tx39.cdl(78):
cdl_option
CYGPKG_HAL_MIPS_MSBFIRST {
packages\hal\mips\tx49\current\cdl\hal_mips_tx49.cdl(119):
cdl_option CYGPKG_HAL_MIPS_MSBFIRST {
packages\hal\mips\upd985xx\current\cdl\hal_mips_upd985xx.cdl(201):
cdl_option CYGPKG_HAL_MIPS_MSBFIRST {
packages\hal\mips\vrc4373\current\cdl\hal_mips_vr4300_vrc4373.cdl(82):
cdl_option CYGPKG_HAL_MIPS_MSBFIRST {
but my target never uses above cdl file.
My target's configuration is like next in ecos.db.
target inserter {
alias { "Hitachi inserter board" }
packages { CYGPKG_HAL_SH
CYGPKG_HAL_SH_SH3
CYGPKG_HAL_SH_SH77X9_inserter
CYGPKG_IO_FLASH
CYGPKG_DEVS_FLASH_SH_inserter
CYGPKG_DEVS_FLASH_AMD_AM29XXXXX
CYGPKG_DEVS_ETH_SMSC_LAN91CXX
CYGPKG_DEVS_ETH_SH_INSERTER
CYGPKG_IO_ETH_DRIVERS
CYGPKG_IO_SERIAL_SH_inserter
CYGPKG_IO_SERIAL_SH_SCIF
}
description "
The inserter target provides the packages needed to run
eCos on a Hitachi Solution Engine 77x9 board."
}
Please tell me where and how to include CYGPKG_HAL_MIPS_MSBFIRST.
I send my ecos.db for reference.
About,
> 2) # define CYG_BYTEORDER as CYG_MSBFIRST (and not as CYG_LSBFIRST).
It
> should be decided based on option 1) actually.
CYG_BYTEORDER is defined as below in
packages\hal\sh\arch\current\include\basetype.h(60)
#ifdef __LITTLE_ENDIAN__
# define CYG_BYTEORDER CYG_LSBFIRST // Little endian
#else
# define CYG_BYTEORDER CYG_MSBFIRST // Big endian
#endif
__LITTLE_ENDIAN__ are defined in next files.
packages\hal\common\current\include\hal_stub.h(100):
#if (CYG_BYTEORDER==CYG_LSBFIRST)
# if !defined(__LITTLE_ENDIAN__)
# define __LITTLE_ENDIAN__
# endif
# if !defined(_LITTLE_ENDIAN)
# define _LITTLE_ENDIAN
# endif
#endif
packages\redboot\current\include\net\net.h(86):
#if (CYG_BYTEORDER == CYG_LSBFIRST)
#ifndef __LITTLE_ENDIAN__
#define __LITTLE_ENDIAN__
#endif
extern unsigned long ntohl(unsigned long x);
extern unsigned short ntohs(unsigned short x);
#else
#define ntohl(x) (x)
#define ntohs(x) (x)
#endif
I think redboot program space is differnt so I could exclude it.
The question is, between basetype.h and hal_stub.h which is included
first ?
I never defined __LITTLE_ENDIAN__, so I thought even right now,
# define CYG_BYTEORDER CYG_MSBFIRST // Big endian
Isn't it?
I look forward your reply.
Thanks in advance.
Masahiro Ariga
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-11-08 9:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 5:37 [ECOS] Building error on CVS checkout sources ariga masahiro
2007-09-14 8:22 ` [ECOS] " Andrew Lunn
2007-09-14 9:38 ` [ECOS] Virtual Vector Configuration Stefan Sommerfeld
2007-09-14 10:17 ` Nick Garnett
2007-10-15 5:59 ` [ECOS] What functions should I call in ethernet drv ? ariga masahiro
2007-10-15 11:20 ` Gary Thomas
2007-10-16 3:04 ` ariga masahiro
2007-10-16 11:08 ` Gary Thomas
2007-10-17 7:41 ` ariga masahiro
2007-10-17 11:32 ` Gary Thomas
2007-10-18 7:17 ` ariga masahiro
[not found] ` <000c01c81151$9add59c0$1c0110ac@ariga>
2007-10-18 11:12 ` Gary Thomas
2007-10-19 4:56 ` ariga masahiro
2007-10-19 9:55 ` Gary Thomas
2007-10-20 6:19 ` ariga masahiro
2007-10-23 8:23 ` ariga masahiro
2007-10-23 8:27 ` Alok Singh
2007-10-23 9:05 ` ariga masahiro
2007-10-25 2:05 ` ariga masahiro
2007-10-30 2:41 ` [ECOS] Can't Connect,TCP CHECKSUM INCORRECT ariga masahiro
2007-10-30 3:02 ` Andrew Lunn
2007-10-30 4:17 ` [ECOS] " Grant Edwards
2007-10-30 8:51 ` Alok Singh
2007-11-06 7:14 ` [ECOS] " ariga masahiro
2007-11-06 7:58 ` Alok Singh
2007-11-06 8:30 ` ariga masahiro
2007-11-06 8:35 ` Andrew Lunn
2007-11-06 23:47 ` ariga masahiro
2007-11-07 1:05 ` ariga masahiro
2007-11-07 7:15 ` ariga masahiro
2007-11-07 8:24 ` ariga masahiro
2007-11-07 11:55 ` Alok Singh
2007-11-08 1:56 ` ariga masahiro
2007-11-08 8:23 ` ariga masahiro
2007-11-09 1:25 ` ariga masahiro
2007-11-13 1:13 ` ariga masahiro
2007-11-16 7:40 ` ariga masahiro
2007-11-08 9:13 ` Alok Singh [this message]
2008-01-07 1:36 ` [ECOS] Wrongfully compiled code ariga masahiro
2007-10-17 8:45 ` [ECOS] What functions should I call in ethernet drv ? ariga masahiro
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=E06E3B7BBC07864CADE892DAF1EB0FBD01FE1345@NT-SJCA-0752.brcm.ad.broadcom.com \
--to=alok.singh@broadcom.com \
--cc=andrew@lunn.ch \
--cc=ariga@link-lab.co.jp \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gary@mlbassoc.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).