• February 23, 2025, 12:04:22 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Cross compile for DNS-321  (Read 8588 times)

madwood

  • Level 1 Member
  • *
  • Posts: 7
Cross compile for DNS-321
« on: March 19, 2009, 07:46:47 AM »

Hi all. Please, let me know if I make any foolish statements.

I'm trying to have a decent nfsd installed on my DNS-321. Currently, the user-space unfs3 provided by fun_plug-0.5 does not fit my needs. I posted my original problem here. In the meantime, I'm trying to compile a kernel-level nfsd.ko module for my DNS-321 kernel.

My DNS-321 is running firmware 1.01 dated 10/09/2008 (according to the internal DNS-321 web pages). The kernel that comes with it is (uname -a):
Linux NAS 2.6.22.7 #105 Tue Sep 23 11:36:49 CST 2008 armv5tejl unknown,
which was compiled in September 2008. Note that the kernel version is 2.6.22.7.

Unfortunately, the d-link GPL section of their ftp website solely provides the linux 2.6.12.6 source. I assume that the .config file in there was already suitably modified for the DNS-321 hardware. I also assume that this is the kernel that comes with the first firmware for it (I didn't check but that should be the case indeed).

My intended course of action now is to get the linux 2.6.22.7 kernel source, use the .config file in the provided DNS-321 GPL linux 2.6.12.6 source tarball and compile a new kernel. Since this is the first time I'm trying to make any drastic changes to my DNS-321, does that sound like a good idea? Is there anything I should be concerned or worried about?

A side question is how different is the cross-compile environment from the already documented DNS-323. The DNS-321 GPL FTP's Readme.txt file says I can use the arm-none-linux-gnueabi-le-softfloat toolchain but I have yet to make it work properly. If anyone has managed to do so, let me know.

Thanks.

I also posted the same message in another forum.
Logged

D-Link Multimedia

  • Poweruser
  • Level 7 Member
  • **
  • Posts: 1066
    • D-link Systems, Inc.
Re: Cross compile for DNS-321
« Reply #1 on: March 19, 2009, 10:19:49 AM »

This is ONLY a support forum for the device and the firmware we maintain. Any modifications to the device are not supported here. On the brighter side NFS is already included in the next firmware so if thats all you need it will take 0 modification to support it ;0.

Logged

madwood

  • Level 1 Member
  • *
  • Posts: 7
Re: Cross compile for DNS-321
« Reply #2 on: March 19, 2009, 10:25:05 AM »

Thanks for the feedback. Sorry for the misplaced post!

I welcome the NFS support on the next firmware! That will save me some time indeed.

Any ETA on the firmware release?

Thank you.
Logged

ceyko

  • Level 2 Member
  • **
  • Posts: 49
Re: Cross compile for DNS-321
« Reply #3 on: March 19, 2009, 07:02:56 PM »

Not to be a smart ass, but hurry up with that firmware. hehe.  Got me all excited. SMTP fix.  NFS (ESX VMs here I come!)...yay.
Logged

mig

  • Level 3 Member
  • ***
  • Posts: 217
Re: Cross compile for DNS-321
« Reply #4 on: March 20, 2009, 12:48:45 AM »

On the brighter side NFS is already included in the next firmware so if thats all you need it will take 0 modification to support it.
Do you know if the next firmware will have NFS support in the kernel  ;D ;D or will the NFS be implemented in user space (unfs3)? :-\
Logged

madwood

  • Level 1 Member
  • *
  • Posts: 7
Re: Cross compile for DNS-321
« Reply #5 on: March 21, 2009, 07:54:29 AM »

By the way, will the planned NFS feature in the next firmware include support for the NFSv3 READDIRPLUS request? Hopefullly it will and will fix my main problem.

Please, let me know.
Logged

bigthrilla

  • Level 1 Member
  • *
  • Posts: 1
Re: Cross compile for DNS-321
« Reply #6 on: April 03, 2009, 06:47:21 AM »

ceyko, mig, madwood, and I must all be thinking the same thing........kernel NFS with READDIRPLUS support.

UNFS just won't cut it for ESX!
Logged