Image activator
Hi, Can someone throw light on what ELF image activators is all about and point me to some good articles on it. Thanks, Akash. * Vtiger Tools * Add to Vtiger * Add Text to Account * Lead * Add Text to Description * Create new Record * Add To Do * Add Event * Add Text to Lead * Add Text to Contact * Account * Add Text to Description * Create new Record * Add To Do * Add Event * Contact * Add Text to Description * Create new Record * Add To Do * Add Event * Convert * Skype * Open Link * * Search * Google * Google Top Result * 'mail' * Bing * Yahoo * * Amazon * Ebay * iTunes * * Social * People LinkedIn * Social Twitter * People Facebook * Images & Video * Google Image * Flickr * Youtube * Google Video * Maps * Google * More Google Maps * Google Maps %hwGoogleMapsCountry% * * from Home * to Home * * from Work * to Work * * Yahoo * Microsoft * * Country Info * Local Time * Weather * News * Search All News * Google News * BBC News * Blog Posts About * References * Wikipedia * Wiktionary * Wikiquote * Merriam-Webster * Wordnik * Britannica * Wolfram Alpha * Google Definition * Google Timeline * Google Finance * * Share Price * Share * Email * Twitter * Facebook * Google Mail * * Blog * Blogger * Wordpress * Tag * Delicious * Blinklist * Digg * Copy * with Link * with Link and Date * Citation * with Formatting * Text * Translate * Arabic * Chinese * French * * German * Greek * Italian * Japanese * * Korean * Norwegian * Russian * Spanish * View * Occurrences * * Highlight * Flow * Sentences with '%selected_phrase%' * Paragraphs with '%selected_phrase%' * * Lift * Hide * Color * Un-highlight * This * Regular * Red * Orange * Yellow * Green * Turquoise * Blue * Purple * Pink * Strong * Red * Yellow * Green * Turquoise * Blue * Purple * Weak * Red * Yellow * Green * Turquoise * Blue * Purple * Grey * Light * Mid * Dark * This Everywhere * Regular * Red * Orange * Yellow * Green * Turquoise * Blue * Purple * Pink * Strong * Red * Yellow * Green * Turquoise * Blue * Purple * Weak * Red * Yellow * Green * Turquoise * Blue * Purple * Grey * Light * Mid * Dark * Background * Regular * Red * Orange * Yellow * Green * Turquoise * Blue * Purple * Pink * Strong * Red * Yellow * Green * Turquoise * Blue * Purple * Weak * Red * Yellow * Green * Turquoise * Blue * Purple * Grey * Light * Mid * Dark * Background Everywhere * Regular * Red * Orange * Yellow * Green * Turquoise * Blue * Purple * Pink * Strong * Red * Yellow * Green * Turquoise * Blue * Purple * Weak * Red * Yellow * Green * Turquoise * Blue * Purple * Grey * Light * Mid * Dark * Page Info * Web Links to This Page * IP2Location * Related Pages via Google * Del.ico.us Bookmarked * * Alexa Traffic Rank * URL Trends Report * Page Rank * Keyword Density * Blog Links to This Page * Wayback Machine * Google Cache * * WHOIS * DNS Info * * View Source * Netcraft Site Report * * * Hyperwords * Edit Menu * Preferenc
minicom freebsd 8.0
Hi, Can some one help me with the steps configuring minicom on freebsd 8.0. I have a serial to usb converter running between my board and host machine. Thanks, Akash. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: minicom freebsd 8.0
Hi, I was referring to minicom command similar to one on linux. On linux the config file is /etc/minirc. and the Serial Device is /dev/ttyUSB0, which was working for me. On freebsd the config file is /usr/local/etc/minicom/minirc., but not sure what to update in the field 'pu port'. I tried with /dev/ugen2.2 but got below error > minicom: cannot open /dev/ugen2.2: Permission denied Please let me know what needs to be updated in the 'pu port' field. Thanks, Akash. ____ From: Fbsd1 To: akash kumar Cc: freebsd-questions@freebsd.org Sent: Wed, 2 June, 2010 2:02:30 PM Subject: Re: minicom freebsd 8.0 akash kumar wrote: > Hi, > > Can some one help me with the steps configuring minicom on freebsd 8.0. I > have a serial to usb converter running between my board and host machine. > Thanks, > Akash. > > I take it a minicom is a external serial modem for internet access over the phone lines. First off you better check if this is a windows modem. Phone modems are manufactured for two target markets, MS/Windows (Winmodems) and every thing else. Winmodems are cheep because the hardware controller function is handled by the software you have to install into MS/Windows. This hardware controller function is normally contained in a chip on the modem circuit board. Winmodems are missing this chip and directs the modem to use driver software running in the MS/Windows system to perform the controller function. The most common Winmodem chips are manufactured by Lucent. There are many versions of this Lucent chip resulting in each chip version needing a different MS/Windows software driver version. Up until version 4.4, FBSD did not have any solution to using Winmodems, but with the release of 4.4 the ports collection now contains the "Linux Winmodem 'ltmdm' driver" which was ported to FBSD. This port is very poorly documented, only works with a limited number of Lucent chip version, and can be somewhat unreliable. Your whole Internet connection is managed by your modem and trying to shoe horn a modem specially manufactured for the MS/Windows operating system into FreeBSD is not the way to achieve a satisfactory dialup Internet connection. Plug the usb to serial converter into a usb port on the pc. Plug the serial cable into the modem and the converter. Power on the minicon, and boot your pc. Check your boot messages for the address of the usb to serial converter and use that address in your ppp config for dialing your ISP. If you can't id the address you need, then post your boot message log here for next step in help. Use dmesg > boot.msg.file to get a copy of the boot log. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: minicom freebsd 8.0
Hi, Finally worked for me. Thanks all for your help. Below are the steps. 1. /var/log/messages has below message when ever usb port is inserted. > Unknown USB device: vendor 0x4348 product* 0x5523* bus uhub2 2. grepping for vendor no. > grep 0x4348 /usr/src/sys/dev/usb/* /usr/src/sys/dev/usb/usbdevs:vendor WCH0x4348QinHeng Electronics > cat /usr/src/sys/dev/usb/usbdevs | grep WCH vendor WCH0x4348QinHeng Electronics /* WCH products */ product WCH CH341SER*0x5523 * CH341/CH340 USB-Serial Bridge product WCH2 CH341SER0x7523CH341/CH340 USB-Serial Bridge 3. After bit of googling with 'CH341/CH340 USB-Serial Bridge', found that specific module is missing. Added uchcom in to the config file and rebuilt the kernel and booted with it. > kldstat -v | grep uchcom 309 uhub/uchcom 4. After rebooting could see below messages i.e device being recognized as the module is already present ugen2.3: at usbus2 ucom0: on usbus2 ucom0: CH340 detected The device is created with name /dev/cuaU0 and it worked finally with minicom. Thanks, Akash. From: C. P. Ghost To: akash kumar Cc: freebsd-questions@freebsd.org Sent: Wed, 2 June, 2010 3:36:54 PM Subject: Re: minicom freebsd 8.0 On Wed, Jun 2, 2010 at 11:30 AM, akash kumar wrote: > Hi, > > I was referring to minicom command similar to one on linux. > On linux the config file is /etc/minirc. and the Serial Device > is /dev/ttyUSB0, which was working for me. > On freebsd the config file is /usr/local/etc/minicom/minirc., > but not sure what to update in the field 'pu port'. > > I tried with /dev/ugen2.2 but got below error >> minicom: cannot open /dev/ugen2.2: Permission denied > > Please let me know what needs to be updated in the 'pu port' field. Ah, okay. ugen is a generic device. I think you can't use that directly if you have a usb-to-serial converter. I guess you need to kldload a kernel module specific to your usb-to-serial converter. For example something like uplcom, umodem etc. This would create a new entry in /dev that you can use in minicom. Permissions for those devices can be set in /etc/devfs.rules (and restarting devfs with /etc/rc.d/devfs restart). You may also want to look at /etc/devd.conf I'm not familiar with usb-to-serial converters, so I can't help more than that. Others may have more experience there. > Thanks, > Akash. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
compiler flag -Werror
Hi all, I am working on building a freebsd kernel for mips. As part of this i built cross tool chain for mips from my host machine(i386). After that i was building my kernel using make buildkernel KERNCONF="configfile" I noticed that the compiler flags -Werror is invoked default with my compiler. I want to remove this flag because all the warning as taken as errors due to which my compilation stops. Can you please help me how/where to remove this flag. Thanks, Bhanu Prakash. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: compiler flag -Werror
Thanks Mark/kitsana for your help. Its working for me now. Thanks, Akash. From: Mark Tinguely To: CyberLeo Kitsana Cc: akash kumar Sent: Thu, 17 June, 2010 1:21:53 AM Subject: Re: compiler flag -Werror CyberLeo Kitsana wrote: > On 06/16/2010 08:02 AM, akash kumar wrote: > >> Hi all, >> >> I am working on building a freebsd kernel for mips. As part of this i built >> cross tool chain for mips from my host machine(i386). >> After that i was building my kernel using make buildkernel >> KERNCONF="configfile" >> >> I noticed that the compiler flags -Werror is invoked default with my >> compiler. I want to remove this flag because all the warning as taken as >> errors due to which my compilation stops. >> >> Can you please help me how/where to remove this flag. > > I have run across this in the past, when building for a VIA C3-2 CPU; so > I have this in my /etc/make.conf: > > # Inline limit warnings? > # Userland: > NO_WERROR=yes > # Kernel: Just turn off inline warnings > WERROR=-Wno-inline -Werror > > The kernel entry is in /sys/conf/kern.pre.mk Mark Tinguely ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
mountroot error with memory based rootfs
Hi, I was trying to build root filesystem in to the kernel (i.e using /dev/md0) for Mips based target boards. In the process i built tool chain and kernel successfully. But when i boot the kernel on the target, it fails to mount the md0 and drops to mountroot prompt. mountroot> ufs:/dev/md0 ROOT MOUNT ERROR If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and the remove invalid mount options from /etc/fstab. Loader variables: vfs.root.mountfrom= vfs.root.mountform.options= I could see that both the above variables are unset and not sure whether this is by default. As i am building a cross kernel, i can't add these options to /boot/loader.conf files which applies to current host machine. Please help me where the above settings need to be added i.e which directory and file for the settings to effect for my target kernel build. Thanks, Akash. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mountroot error with memory based rootfs
Hi, The root file system was built commenting out compact flash and enabling md0 as below in the config file for my target arch. #device cf #optionsROOTDEVNAME=\"ufs:cf0s1\" # Use the following for RFS in mem-device options MD_ROOT options ROOTDEVNAME = \"ufs:md0\" options MD_ROOT_SIZE = 7264 After the kernel was built and installed using 'make buildkernel KERNCONF="configfile" and make installkernel commands. Please let me know if you need any more info. Thanks, Bhanu Prakash. ________ From: Tim Judd To: akash kumar Sent: Fri, 18 June, 2010 7:50:14 AM Subject: Re: mountroot error with memory based rootfs On 6/17/10, akash kumar wrote: > Hi, > > I was trying to build root filesystem in to the kernel (i.e using /dev/md0) > for Mips based target boards. In the process i built tool chain and kernel > successfully. > But when i boot the kernel on the target, it fails to mount the md0 and > drops to mountroot prompt. > > mountroot> ufs:/dev/md0 > ROOT MOUNT ERROR > If you have invalid mount options, reboot, and first try the following from > the loader prompt: > > set vfs.root.mountfrom.options=rw > > and the remove invalid mount options from /etc/fstab. > > Loader variables: > vfs.root.mountfrom= > vfs.root.mountform.options= > > I could see that both the above variables are unset and not sure whether > this is by default. As i am building a cross kernel, i can't add these > options to /boot/loader.conf files which applies to current host machine. > > Please help me where the above settings need to be added i.e which directory > and file for the settings to effect for my target kernel build. > > Thanks, > Akash. > > Please give details on how the root filesystem image is built. What works is to format the rootfs image without a partition or bsdlabel. It is just unable to mount the image as specified. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
preemption enable/disable routines
Hi, Can some one tell me the routines in freebsd to enable and disable preemption. In linux we have preempt_enable and preempt_disable which does the functionality. In case freebsd, doesnot have such routines can i used mtx_lock_spin() to do the same? Thanks, Akash. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
