From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.fst.it ([213.255.39.254] helo=fst.it) by pentafluge.infradead.org with smtp (Exim 4.22 #5 (Red Hat Linux)) id 19tky9-0002AV-L5 for ; Mon, 01 Sep 2003 10:27:29 +0100 Message-ID: <041c01c3706b$63cd8210$a970a8c0@topo> From: "Luca Contini" To: "J.D. Bakker" References: <023501c36e31$81a4a610$a970a8c0@topo> <024b01c36e35$62241600$a970a8c0@topo> Date: Mon, 1 Sep 2003 11:28:17 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit cc: "linux-mtd-request@lists.infradead.org" Subject: Re: latest MTD snapshot List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > At 15:56 +0200 29-08-2003, Luca Contini wrote: > > > At 15:28 +0200 29-08-2003, Luca Contini wrote: > > > >What Am I missing? > >> > >> 1) Which kernel version ? > > > >2.4.18-rmk6-swl6 > > That's a pretty ancient kernel (almost 18 months old). You may want > to retry with 2.4.21-rmk1 (works fine on the LART, which is also > arm-based). I've tried kernel 2.4.21, but the patch I have from samsung didn't work. So the point is: to make the new MTD subsystem work with my old 2.4.18 kernel. Is it possible and how? > > > > 3) Any particular reason why you don't use the patchin.sh script ? I > >> know, you 'only' need mtdblock, but partial installs tend to create > >> no end of trouble. > > > >I just thought it was easiest to do it manually just for mtdblock device. > >I've copied the snapshot to ../linux/drivers/mtd/util/snapshot and tried the > >patchin.sh: > >[root@Lab patches]# patchin.sh > >Directory does not exist or is not a kernel source directory > > You must give it the path to your kernel tree as an argument (as > documented on http://www.linux-mtd.infradead.org/). > > HTH, > > JDB. > -- > LART. 250 MIPS under one Watt. Free hardware design files. > http://www.lart.tudelft.nl/ > >